This document describes the process of doing an official release of Myriad.
Some general guidelines
- Mark the JIRAs that needs to go into a release.
- Choose a "Release Manager". It's highly recommended that the Release Manager should read the docs listed under "Useful Links" section.
- Agree upon a potential release date.
- Submit PRs. Review PRs submitted by others.
Prerequisites
Apache requires signing the release artificats/archives using a OpenPGP compatible ASCII armored detached signature. Please read this document.
Ensure that the "Release Manager" has a GPG key or generate a new one, e.g., using
gpg
--gen-key. Make sure to generate a RSA key with at least 4096 bits.Add your GPG public key to the Apache Myriad dist repository in the KEYS file.
- Submit your GPG public key to a keyserver, e.g. MIT PGP Public Key Server.
Add your GPG fingerprint to your Apache account.
Just before a release
- Ensure all the outstanding PRs are merged.
- (Re)Read Apache's Release Check List.
- It is recommended to download the latest master and run Apache RAT tool on the to-be-released code base to fix any missing Apache License headers.
Running Apache RAT tool
Clone the latest master: git clone https://github.com/apache/incubator-myriad.git
Get Apache RAT jar: wget http://central.maven.org/maven2/org/apache/rat/apache-rat/0.11/apache-rat-0.11.jar
Add any missing Apache License headers: java -jar apache-rat-0.11.jar incubator-myriad/ -a -f
Verify if RAT has added any license headers: cd incubator-myriad ; git status
If any of the sources had missing license headers, submit a PR.
Note:
- Here are guidelines on which sources should have the license headers.
Preparing a Release Candidate
Signing a Release Candidate
Publishing a Release Candidate
Voting
Post Voting Actions
Useful Links