Polishing release procedures.
This commit is contained in:
10
README.adoc
10
README.adoc
@@ -47,7 +47,7 @@ But part of the release process requires a local check, which DOES depend upon y
|
||||
2. With the release tagged, update the release branch to the newly created tag.
|
||||
+
|
||||
----
|
||||
% git checkout -b release-3.1.x
|
||||
% git checkout release-3.1.x
|
||||
% git reset --hard <tag>
|
||||
----
|
||||
+
|
||||
@@ -64,13 +64,7 @@ But part of the release process requires a local check, which DOES depend upon y
|
||||
% git push -f origin release-3.1.x
|
||||
----
|
||||
+
|
||||
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 `3.1.x` branch for next version's snapshots.
|
||||
. Once completed, push the `3.1.x` branch for next version's snapshots.
|
||||
+
|
||||
----
|
||||
% git checkout 3.1.x
|
||||
|
||||
Reference in New Issue
Block a user