snazy opened a new pull request, #485:
URL: https://github.com/apache/polaris/pull/485

   Introduce a couple of shell scripts to automate the release process. Some 
docs are included under `releases/README.md`.
   
   Generally, releases at the ASF follow the following workflow:
   1. Draft a release
   2. Start a VOTE on the dev mailing list
   3. If the VOTE fails, the release has failed - "go to step 1"
   4. If the VOTE passes, publish the release
   
   The above process is, without release branches, reflected in the scripts:
   1. `releases/bin/draft-release.sh --major <major-version-number> --minor 
<minor-version-number> --commit <Git-commit-ID>`
   2. if the vote passes: `releases/bin/publish-release.sh --major 
<major-version-number> --minor <minor-version-number>`
   3. if the vote fails, just run `draft-release.sh` again
   
   The change includes scripts to handle version branches, however, using those 
is not required for the two release scripts above.
   
   It's important to know that the scripts handle changes to the `version.txt` 
file and that a specific syntax for Git tags is expected, which is required to 
automatically use/generate RC and final versions, including the artifact 
publishing via Sonatype.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to