comparison README.rst @ 6090:66d146b88c45 stable

readme: update release checklist (mostly formatting)
author Anton Shestakov <av6@dwimlabs.net>
date Sat, 20 Nov 2021 08:55:43 +0300
parents 2068ff9ad72a
children 91cbb952676e
comparison
equal deleted inserted replaced
6088:ee1097379752 6090:66d146b88c45
197 byteify-strings:mode.output = pipe 197 byteify-strings:mode.output = pipe
198 198
199 Release Checklist 199 Release Checklist
200 ================= 200 =================
201 201
202 * use contrib/merge-test-compat.sh to merge with the test compatibility
203 branches,
204
202 * make sure the tests are happy on all supported versions, 205 * make sure the tests are happy on all supported versions,
203 206
204 You can use the `contrib/merge-test-compat.sh` to merge with the test 207 * make sure there is no code difference between the compatibility branches and
205 compatibility branches. 208 stable (no diff within hgext3rd/),
206 209
207 * make sure there is no code difference between the compat branches and stable 210 * update the ``testedwith`` variable for all extensions (remove '.dev'):
208 (no diff within `hgext3rd/`),
209
210 * update the `testedwith` variable for all extensions (remove '.dev'):
211 211
212 - hgext3rd/evolve/metadata.py 212 - hgext3rd/evolve/metadata.py
213 - hgext3rd/topic/__init__.py 213 - hgext3rd/topic/__init__.py
214 - hgext3rd/pullbundle.py 214 - hgext3rd/pullbundle.py
215 215
216 * make sure the changelog is up to date, 216 * make sure CHANGELOG is up-to-date,
217 217
218 * add a date to the changelog entry for the target version, 218 * add a date to the CHANGELOG entry for the target version,
219 219
220 * update the `__version__` field of all relevant extensions: 220 * update the ``__version__`` field of all relevant extensions:
221 221
222 - hgext3rd/evolve/metadata.py 222 - hgext3rd/evolve/metadata.py
223 - hgext3rd/topic/__init__.py 223 - hgext3rd/topic/__init__.py
224 - hgext3rd/pullbundle.py (if touched) 224 - hgext3rd/pullbundle.py (if touched)
225 225
226 * create a new Debian entry: 226 * create a new Debian changelog entry:
227 227
228 - debchange --newversion x.y.z-1 "new upstream release" 228 - debchange --newversion x.y.z-1 "new upstream release"
229 - debchange --release 229 - debchange --release
230 230
231 * sanity check install and sdist targets of setup.py: 231 * sanity check install and sdist targets of setup.py:
233 - python setup.py install --home=$(mktemp -d) 233 - python setup.py install --home=$(mktemp -d)
234 - python setup.py sdist 234 - python setup.py sdist
235 235
236 * tag the commit, 236 * tag the commit,
237 237
238 * move ``@`` bookmark to the new tag,
239
238 * push and publish the tag, 240 * push and publish the tag,
239 241
240 * upload the tarball to PyPI, 242 * upload the tarball to PyPI,
241 243
242 * make an announcement on evolve-testers@mercurial-scm.org (possibly on 244 * make an announcement on evolve-testers@mercurial-scm.org and
243 mercurial@mercurial-scm.org too), 245 mercurial@mercurial-scm.org,
244 246
245 * bump versions of all extensions and add '.dev' (see existing commits as an 247 * bump versions of all extensions and add ``.dev`` (see existing commits as an
246 example): 248 example):
247 249
248 - hgext3rd/evolve/metadata.py 250 - hgext3rd/evolve/metadata.py
249 - hgext3rd/topic/__init__.py 251 - hgext3rd/topic/__init__.py
250 - hgext3rd/pullbundle.py 252 - hgext3rd/pullbundle.py
251 253
252 The version we use on the stable branch during development should be 254 Version bump rules:
253 `x.y.z+1.dev`. The version of the default branch should be `x.y+1.0.dev`. 255
256 - stable branch x.y.z+1.dev
257 - default branch x.y+1.0.dev
254 258
255 * merge stable into default. 259 * merge stable into default.