Update release process a bit

[arvados-dev.git] / cmd / art / TASKS

diff --git a/cmd/art/TASKS b/cmd/art/TASKS
index 4fdee2cf083dd15e00652bacb076134a53d3b848..5522dda3c8753d5496baf30c8a680acd636950c7 100644 (file)
--- a/cmd/art/TASKS
+++ b/cmd/art/TASKS
@@ -1,19 +1,27 @@
-Prepare release branch
+Prepare X.Y-staging branch
+Update the "Upgrading Arvados and Release notes" doc page (main and release branch), update provision.sh, formula and arvbox to point to release
+Ensure that the entire automated testing pipeline is passing on Jenkins
 Review release branch
+Draft release notes and publish them to www-dev
+Review release notes
 Create next redmine release
-Record git commit
 Build RC packages
-Draft release notes
-Review release notes
-Test installer
-Deploy RC packages to playground
-Run test pipeline
-Sign off
+Build RC arvados/jobs image
+Ensure installer tests are passing
+Build compute image & deploy RC packages to playground
+Run bam-to-vcf demo pipeline
+Manual testing
+Approve RC for release
+Build final release packages
+Publish stable arvados/jobs Docker image
 Push packages to stable
-Publish docker image, python and ruby packages
-Publish formula/installer for release
-Publish arvbox image
-Tag commits
-Update doc site
-Publish release on arvados.org
-Send out release notification
+Publish Python and Ruby packages
+Publish Java package
+Publish R package
+Publish arvados/arvbox-demo image
+Tag commits, fast-forward X.Y-release branch to match X.Y-staging
+Ensure doc.arvados.org is up to date
+Merge release notes (step 6) from "develop" to "main" on arvados.org
+Send out release announcements
+Major releases only: Copy "run-tests" jobs in jenkins
+Add the release to zenodo.org