dev:evergreen:release_checklist
This is an old revision of the document!
Evergreen release checklist
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.
Checklist
- buildmaster cuts the release tarball and uploads to evergreen-ils.org
- buildmaster uploads the ChangeLog to evergreen-ils.org
- buildmaster creates a point-to-point version upgrade script and adds it to the Open-ILS/src/sql/Pg/version_upgrade/ directory
- buildmaster creates the Windows staff client, computes the md5 checksum, and uploads to evergreen-ils.org
- DIG release coordinator makes final edits to release notes, reviews for completeness
- 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)
- 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)
- (pre-beta only) release-lead coordinates with feature developers to ensure that branches were merged properly
- bug-wrangler changes "Fix committed" bugs to "Fix released" for that milestone
- bug-wrangler creates new milestone for that release
- web-team-member updates web site:
- Install instructions (convert README to HTML via asciidoc and post to /var/www/open-ils.org/documentation/install/)
- Release notes (convert docs/RELEASE_NOTES_#_#.txt to HTML via asciidoc and post to /var/www/open-ils.org/documentation/release/)
- Download page (update link to tarball, md5sum, install docs, release notes)
- release-lead Announces release on mailing list & blog, updates Wikipedia, foss4lib, etc. See more information
- outreach committee/ Writes press release with review and quote from release-lead and sends out to contacts on publicity checklist ===== Release Team Members ===== ==== Evergreen 2.3 ==== ^ Responsibility ^ Member(s) ^ | release-lead | Bill Erickson | | release-notes-writer | now a community effort | | testers | | | bug-wrangler | Jason Stephenson | | web-team-member | | ==== Evergreen 2.2 ==== ^ Responsibility ^ Member(s) ^ | release-lead | Lebbeous Fogle-Weekley | | release-notes-writer | now a community effort | | testers | Michael Peters | | bug-wrangler | Jason Stephenson, Ben Shum | | web-team-member | Anoop Atre | ==== Evergreen 2.1 ==== ^ Responsibility ^ Member(s) ^ | release-lead | Dan Scott | | release-notes-writer | Galen Charlton, Mike Rylander | | testers | | | bug-wrangler | Jason Stephenson | | web-team-member | Anoop Atre, Amy Terlaga | ==== Evergreen 2.0 ==== ^ Responsibility ^ Member(s) ^ | release-lead | Jason Stephenson | | staff-client-packager | Jason Etheridge, Brian Feifarek, Ben Shum | | release-notes-writer | Anoop Atre, Mike Rylander | | testers | several | | bug-wrangler | Jason Stephenson | | web-team-member | Anoop Atre, Amy Terlaga |
dev/evergreen/release_checklist.1478985490.txt.gz · Last modified: 2022/02/10 13:34 (external edit)