-
Notifications
You must be signed in to change notification settings - Fork 2
Release Checklist
Erik Massop edited this page Nov 4, 2017
·
1 revision
This is a list of things that should be done or checked before, and when doing a release.
- Prepare a bottle of wine. To be opened AFTER the release is done :)
- Create release page titled Release:
- Categorise under :Category:Releases ()
- Make sure API-versions are increased if needed.
- Make sure so-versions are increased if needed.
- Sleep. Make sure you are not tired when doing release, to minimize risks of mistakes.
- Check if there is work needed on articles in :Category:Articles to be merged at next release
- wiki:
- check and merge articles or sections in :Category:Articles to be merged at next release.
- README in sync with 'Read me first!' wiki page
- INSTALL in sync with 'Installation instructions' wiki page
- news post Template:News, Template:ShortNews
- release status box Project Status
- Version number set
- Release snapshot ready (use release.py) & uploaded to sourceforge
- Update freshmeat page
- Send announcement to mailinglist
- doxygen + pydoc + rdoc docs generated & published to exodus
- Update History page
Other things which currently would not really be possible:
- no release critical bugs? - criteria?
- pass build and runtime tests?
Content is available under GNU Free Documentation License 1.2 unless otherwise noted.
- Community
- Development