1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
|
%global _empty_manifest_terminate_build 0
Name: python-autorelease
Version: 0.4.0
Release: 1
Summary: Tools to keep the release process clean.
License: MIT
URL: https://github.com/dwhswenson/autorelease
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/9f/43/42451d942fec7bff15de925024d0b923c5fd83c5aec14f1d7900f732b65d/autorelease-0.4.0.tar.gz
BuildArch: noarch
Requires: python3-packaging
Requires: python3-pyyaml
Requires: python3-gitpython
Requires: python3-future
Requires: python3-requests
Requires: python3-dateutil
Requires: python3-click
%description
[](http://autorelease.readthedocs.io/en/latest/?badge=latest)
[](https://travis-ci.org/dwhswenson/autorelease)
[](https://ci.appveyor.com/project/dwhswenson/autorelease/branch/master)
# Autorelease
Release management for GitHub and continuous integration, based on branches.
The basic philosophy is to maintain development branches (which always have
development versions of the code) and release branches (which always have
release versions of the code). The workflow for a release is therefore:
1. Update the version for release and make a PR to a stable branch; the top
post will be the release notes.
2. Merge the PR.
That's it. Autorelease handles the rest.
When you make the PR to a stable branch, Autorelease will deploy the package to
testpypi, and re-download it and test it again. This ensures that you don't
publish broken packages. After you merge to the stable branch, Autorelease will
cut a new release on GitHub, and then publish the release on PyPI.
Tools included:
* Travis config imports and scripts to automatically test-deploy on testpypi,
then cut a GitHub release, then deploy to PyPI.
* Vendor-able GitHub Actions workflows for test-deploy, GitHub release, and
PyPI deploy.
* Vendor-able `version.py` that gives one true location for version
(`setup.cfg`) while also enabling developer installs to give full and correct
version information.
* Vendor-able `setup.py` that keeps all user-required information in the
`setup.cfg`.
* Script to draft release notes based on labels on merged PRs.
If you're a Python developer who uses Travis and GitHub, Autorelease handles
everything related to releasing to PyPI.
%package -n python3-autorelease
Summary: Tools to keep the release process clean.
Provides: python-autorelease
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-autorelease
[](http://autorelease.readthedocs.io/en/latest/?badge=latest)
[](https://travis-ci.org/dwhswenson/autorelease)
[](https://ci.appveyor.com/project/dwhswenson/autorelease/branch/master)
# Autorelease
Release management for GitHub and continuous integration, based on branches.
The basic philosophy is to maintain development branches (which always have
development versions of the code) and release branches (which always have
release versions of the code). The workflow for a release is therefore:
1. Update the version for release and make a PR to a stable branch; the top
post will be the release notes.
2. Merge the PR.
That's it. Autorelease handles the rest.
When you make the PR to a stable branch, Autorelease will deploy the package to
testpypi, and re-download it and test it again. This ensures that you don't
publish broken packages. After you merge to the stable branch, Autorelease will
cut a new release on GitHub, and then publish the release on PyPI.
Tools included:
* Travis config imports and scripts to automatically test-deploy on testpypi,
then cut a GitHub release, then deploy to PyPI.
* Vendor-able GitHub Actions workflows for test-deploy, GitHub release, and
PyPI deploy.
* Vendor-able `version.py` that gives one true location for version
(`setup.cfg`) while also enabling developer installs to give full and correct
version information.
* Vendor-able `setup.py` that keeps all user-required information in the
`setup.cfg`.
* Script to draft release notes based on labels on merged PRs.
If you're a Python developer who uses Travis and GitHub, Autorelease handles
everything related to releasing to PyPI.
%package help
Summary: Development documents and examples for autorelease
Provides: python3-autorelease-doc
%description help
[](http://autorelease.readthedocs.io/en/latest/?badge=latest)
[](https://travis-ci.org/dwhswenson/autorelease)
[](https://ci.appveyor.com/project/dwhswenson/autorelease/branch/master)
# Autorelease
Release management for GitHub and continuous integration, based on branches.
The basic philosophy is to maintain development branches (which always have
development versions of the code) and release branches (which always have
release versions of the code). The workflow for a release is therefore:
1. Update the version for release and make a PR to a stable branch; the top
post will be the release notes.
2. Merge the PR.
That's it. Autorelease handles the rest.
When you make the PR to a stable branch, Autorelease will deploy the package to
testpypi, and re-download it and test it again. This ensures that you don't
publish broken packages. After you merge to the stable branch, Autorelease will
cut a new release on GitHub, and then publish the release on PyPI.
Tools included:
* Travis config imports and scripts to automatically test-deploy on testpypi,
then cut a GitHub release, then deploy to PyPI.
* Vendor-able GitHub Actions workflows for test-deploy, GitHub release, and
PyPI deploy.
* Vendor-able `version.py` that gives one true location for version
(`setup.cfg`) while also enabling developer installs to give full and correct
version information.
* Vendor-able `setup.py` that keeps all user-required information in the
`setup.cfg`.
* Script to draft release notes based on labels on merged PRs.
If you're a Python developer who uses Travis and GitHub, Autorelease handles
everything related to releasing to PyPI.
%prep
%autosetup -n autorelease-0.4.0
%build
%py3_build
%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .
%files -n python3-autorelease -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Wed May 10 2023 Python_Bot <Python_Bot@openeuler.org> - 0.4.0-1
- Package Spec generated
|
