From 4acf98410f933d87f00d7a9c9668465c62be3ec4 Mon Sep 17 00:00:00 2001 From: "Greg L. Turnquist" Date: Mon, 24 Jan 2022 12:44:17 -0600 Subject: [PATCH] Polishing. --- README.adoc | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/README.adoc b/README.adoc index b63be224..f489f05d 100644 --- a/README.adoc +++ b/README.adoc @@ -64,11 +64,23 @@ But part of the release process requires a local check, which DOES depend upon y ---- % git push -f origin release ---- ++ +5. For milestones and release candidates, verify the artifacts on artifactory. +6. For releases, login to maven central. +* Verify the release. +* Close the repository. +* Release the repository. +7. Announce on VMware Slack. +8. Once completed, push the `main` branch for next version's snapshots. ++ +---- +% git checkout main +% git push +% git push --tags +---- -NOTE: You can chain the previous set of commands together using `&&`. - -The pipeline will build and release the "release" branch. It will also build a new a new snapshot and stage it on artifactory. -For releases that go to Maven Central, the user much manually check out and verify the artifacts before releasing them. +The pipeline will build and release the "release" branch on artifactory for milestones and RCs. +For releases, they are sent to maven central. === Running CI tasks locally