178 

   179 Release Checklist

   180 =================

   181 

   182 * make sure the tests are happy on all supported versions,

   183 

   184   You can use the `contrib/merge-test-compat.sh` to merge with the test

   185   compatibility branches.

   186 

   187 * make sure there is no code difference between the compat branches and stable

   188   (no diff within `hgext3rd/`),

   189 

   190 * update the `testedwith` variable for all extensions (remove '.dev'):

   191 

   192   - hgext3rd/evolve/metadata.py

   193   - hgext3rd/topic/__init__.py

   194   - hgext3rd/pullbundle.py

   195 

   196 * make sure the changelog is up to date,

   197 

   198 * add a date to the changelog entry for the target version,

   199 

   200 * update the `__version__` field of all relevant extensions:

   201 

   202   - hgext3rd/evolve/metadata.py

   203   - hgext3rd/topic/__init__.py

   204   - hgext3rd/pullbundle.py (if touched)

   205 

   206 * create a new Debian entry:

   207 

   208   - debchange --newversion x.y.z-1 "new upstream release"

   209   - debchange --release

   210 

   211 * sanity check install and sdist targets of setup.py:

   212 

   213   - python setup.py install --home=$(mktemp -d)

   214   - python setup.py sdist

   215 

   216 * tag the commit,

   217 

   218 * push and publish the tag,

   219 

   220 * upload the tarball to PyPI,

   221 

   222 * make an announcement on evolve-testers@mercurial-scm.org (possibly on

   223   mercurial@mercurial-scm.org too),

   224 

   225 * bump versions of all extensions and add '.dev' (see existing commits as an

   226   example):

   227 

   228   - hgext3rd/evolve/metadata.py

   229   - hgext3rd/topic/__init__.py

   230   - hgext3rd/pullbundle.py

   231 

   232   The version we use on the stable branch during development should be

   233   `x.y.z+1.dev`. The version of the default branch should be `x.y+1.0.dev`.

   234 

   235 * merge stable into default.