Release Checklist » History » Revision 4
- Create an issue for the release.
- Add each of the following steps (starting at step 1) as tasks with the step number in the subject
- Assign each task
- The current task goes into the "In Progress" column
- When the current task is finished, move it to resolved, and move the next task into "In Progress"
- Notify the assignee of the next task that it is ready to begin
|Write lots of great code, build new features
|Go through https://dev.arvados.org/projects/arvados/wiki/Manual_testing_plan
|Prepare release branch ready for release candidate
|Review release branch, make sure all commits that need to be in the release are in the release, make sure that dependencies of Python and Ruby packages have upper version pins (to ensure that 3rd party dependencies updated post-stable-release don't break our code)
|Create a redmine release for the next patch release beyond this one so that future bugfixes can be assigned to it, if there's a chance that such a release will be made.
|Record git commits that will be used to build the release following the instructions at https://dev.arvados.org/projects/ops/wiki/Arvados_Release_lifecycle#Cut-off-commits-Choosing-a-Version
|Build release candidate packages
|Send out draft release notes
|Review release notes
|Deploy RC packages to playground 1
|Run bam-to-vcf pipeline on playground 1
|Deploy RC packages to su92l 1
|Test playground/su92l 1
|Sign off on last built RC as the release
|Push packages to stable repos (https://dev.arvados.org/projects/ops/wiki/Promoting_Packages_to_Stable)
|Publish arvados/jobs docker image, Python packages and Ruby gems
|Tag the commits in each repo used to build the release in git
|Add release notes to https://arvados.org/release-notes/X.Y.Z.html and Update release list at https://arvados.org
|Send release notes to arvados and arvados-dev mailing list, tweet from the Arvados account about the new release, announce on gitter, notify customers, etc
|Duplicate the jenkins configuration for tests to versioned names so that future point releases remain testable after master moves on
1 If issues are discovered in these steps, get a fix developed, reviewed and merged, and then update the ops ticket from step 3 with the relevant new git commit(s), notify ops, and resume the checklist from step 4.