-
-
Notifications
You must be signed in to change notification settings - Fork 384
pgRouting Release Process Checklist
Stephen Woodbridge edited this page Sep 19, 2013
·
15 revisions
This page hopefully documents that things that need to get done to make a product release.
TODO: We need to add missing steps, and add details for how to do each step.
More ideas: https://github.com/postgis/postgis/blob/svn-trunk/HOWTO_RELEASE
- Hopefully the release goals have been set and completed
- All tests run, don't forget to check the Windows build-bot
- Add changes have been reflected in the doc files
- Update or create release notes
- We have run through appropriate alpha, beta, RCn steps, gotten feedback and resolved issues
- CMakeLists.txt has been updated with the correct version number
- An appropriate tag has been created for this release
- Edit VERSION to be "v2.0.0-0- master"
- Edit doc/test/utilities-any.rest and update version numbers
- Build and run final tests and verify version numbers
- Edit doc/index.html.in and add new release to it, remove obsolete stuff
- Merge stable release into master and build and test here
- Push code and tag to github
- Documentation has been build and pushed to gh-pages (also
index.htmlhas been modified) - The source tarball link from Github has been updated in the docs and on the download page
- Project website has been updated
- Upstream Linux distribution packagers have been notified
- who ...
- Upstream Windows distribution packagers have been notified
- Regina <lr (at) pcorp (dot) us>
- An announcement has been written, reviewed sent to -users, -dev, postgis-users, OSGeo-discuss, OSGeo-Announce mailing list.