Mercurial > evolve
comparison .gitlab/issue_templates/new-version.md @ 5117:60e2a6a11d62 stable
heptapod: add an issue template for new version
author | Pierre-Yves David <pierre-yves.david@octobus.net> |
---|---|
date | Sat, 01 Feb 2020 11:24:46 +0100 |
parents | |
children | aff0292c00d9 |
comparison
equal
deleted
inserted
replaced
5116:2392fe0e745a | 5117:60e2a6a11d62 |
---|---|
1 This is the actual check list for releasing evolve version X.Y.Z | |
2 | |
3 More details in the [README file](README#L179). | |
4 | |
5 Preparation | |
6 | |
7 * [ ] merges with compatibility branches | |
8 * [ ] compatibility tests are happy | |
9 * [ ] update `testedwith` field | |
10 * [ ] make sure the changelog is up to data | |
11 * [ ] [prepare an announcement for the list/website](https://mypads.framapad.org/mypads/?/mypads/group/octobus-public-5d3rw470w/pad/view/evolution-announce-iswcp7qx) | |
12 * [ ] sanity check install and sdist targets of setup.py | |
13 | |
14 Releasing | |
15 | |
16 * [ ] add the current date to the changelog | |
17 * [ ] update the `__version__` field of all relevant extensions | |
18 * [ ] create a new Debian entry | |
19 * [ ] tag the version | |
20 * [ ] push/publish the tag to the main repository | |
21 * [ ] upload the tarball to PyPI | |
22 * [ ] add `.dev` to the `__version__` field | |
23 * [ ] merge stable into default |