Tweak to the order of release tasks: the reference to the default

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

diff --git a/cmd/art/TASKS b/cmd/art/TASKS
index 9aa1a3b9482bf469dee2411f4b686dc2bac43709..64b060e34e23e9b59550a225522408d3cd5e7c1f 100644 (file)
--- a/cmd/art/TASKS
+++ b/cmd/art/TASKS
@@ -1,4 +1,4 @@
-Prepare release branch
+Prepare release branches
 Update the "Upgrading Arvados and Release notes" doc page (main and release branch)
 Ensure that the entire automated testing pipeline is passing on Jenkins
 Manual testing
@@ -7,17 +7,22 @@ Create next redmine release
 Draft release notes and publish them to www-dev
 Review release notes
 Build RC packages
-Test installer
-Deploy RC packages to playground
-Run bam-to-vcf pipeline pipeline
+Build RC arvados/jobs image
+Ensure installer tests are passing
+Build compute image & deploy RC packages to playground
+Run bam-to-vcf demo pipeline
 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 Python and Ruby packages
+Publish Java package
+Publish R package
 Publish arvados/arvbox-demo image
+Update provision.sh, formula and arvbox to point to release
 Tag commits
-Update doc site
-Merge release notes (step 6) form "develop" to "main" and publish release on arvados.org
-Send out release notification
+Ensure doc.arvados.org has new version
+Merge release notes (step 7) 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