We have started to develop a release checklist (from the last Developer Meeting).

We need to enhance and agree on the checklist (ideally each step links to a more detailed process, and we're probably missing steps).

We should assign positions to names for each release so it is clear who does what.

We would like a "release coordinators" mailing list to, uhh, help coordinate the release.

We should adopt this checklist as a process, then we probably copy the page prior to each release with the names for each position.

1. release-lead cuts the release tarball and uploads to evergreen-ils.org
2. release-lead uploads the ChangeLog to evergreen-ils.org
3. evergreen-dev creates a point-to-point version upgrade script and adds it to the Open-ILS/src/sql/Pg/version_upgrade/ directory
4. staff-client-packager creates the Windows staff client, computes the md5 checksum, and uploads to evergreen-ils.org
5. release-notes-writer puts final release notes on evergreen-ils.org / into official documentation / wherever
6. testers run test cases and file bugs for broken test cases (QA team members need to add/extend/update test cases during the release cycle)
7. testers test point-to-point version upgrade script to ensure that database schema & data is successfully migrated from previous release to new release (arguably should be part of test cases along with installing a clean database schema)
8. (pre-beta only) release-lead coordinates with feature developers to ensure that branches were merged properly
9. bug-wrangler changes "Fix committed" bugs to "Fix released" for that milestone
10. bug-wrangler creates new milestone for that release
11. web-team-member updates download page with new release
12. communication-team-member announces release on mailing list / blog and updates wikipedia / freshmeat