Apache TVM (incubating) Release Process¶
The release manager role in TVM means you are responsible for a few different things:
Preparing release notes
Preparing your setup
Preparing for release candidates
Cutting a release branch
Informing the community of timing
Making code changes in that branch with necessary version updates
Running the voting process for a release
Creating release candidates
Calling votes and triaging issues
Finalizing and posting a release:
Updating the TVM website
Finalizing release notes
Announcing the release
Prepare the Release Notes¶
Release note contains new features, improvement, bug fixes, known issues and deprecation, etc. TVM provides monthly dev report collects developing progress each month. It could be helpful to who writes the release notes.
It is recommended to open a Github issue to collect feedbacks for the release note draft before cutting the release branch.
Prepare the GPG Key¶
You can skip this section if you have already uploaded your key.
After generating the gpg key, you need to upload your key to a public key server. Please refer to https://www.apache.org/dev/openpgp.html#generate-key for details.
If you want to do the release on another machine, you can transfer your gpg key to that machine via the
gpg --export and
gpg --import commands.
The last step is to update the KEYS file with your code signing key https://www.apache.org/dev/openpgp.html#export-public-key. Check in the changes to the master branch.
Cut a Release Candidate¶
To cut a release candidate, one needs to first cut a branch using selected version string, e.g.,
git clone https://github.com/apache/incubator-tvm.git cd incubator-tvm/ git branch v0.6.0 git push --set-upstream origin v0.6.0
Go to the GitHub repositories “releases” tab and click “Draft a new release”,
Provide the release tag in the form of “v1.0.0.rc0” where 0 means it’s the first release candidate
Select the commit by clicking Target: branch > Recent commits > $commit_hash
Copy and paste release note draft into the description box
Select “This is a pre-release”
Click “Publish release”
Notice that one can still apply changes to the BRANCH after the cut, while the TAG is fixed. If any change is required for this release, a new TAG has to be created.
Remove previous release candidate (if applied),
git push --delete origin 0.6.0.rc1
Create source code artifacts,
git clone email@example.com:apache/incubator-tvm.git apache-tvm-src-v0.6.0.rc0-incubating cd apache-tvm-src-v0.6.0.rc0-incubating git checkout v0.6 git submodule update --init --recursive git checkout v0.6.0.rc0 rm -rf .DS_Store find . -name ".git*" -print0 | xargs -0 rm -rf cd .. brew install gnu-tar gtar -czvf apache-tvm-src-v0.6.0.rc0-incubating.tar.gz apache-tvm-src-v0.6.0.rc0-incubating
Use your GPG key to sign the created artifact. First make sure your GPG is set to use the correct private key,
$ cat ~/.gnupg/gpg.conf default-key F42xxxxxxxxxxxxxxx
Create GPG signature as well as the hash of the file,
gpg --armor --output apache-tvm-src-v0.6.0.rc0-incubating.tar.gz.asc --detach-sig apache-tvm-src-v0.6.0.rc0-incubating.tar.gz shasum -a 512 apache-tvm-src-v0.6.0.rc0-incubating.tar.gz > apache-tvm-src-v0.6.0.rc0-incubating.tar.gz.sha512
Upload the Release Candidate¶
Edit the release page on Github and upload the artifacts created by the previous steps.
The release manager also needs to upload the artifacts to ASF SVN,
# the --depth=files will avoid checkout existing folders svn co --depth=files "https://dist.apache.org/repos/dist/dev/incubator/tvm" svn-tvm cd svn-tvm mkdir tvm-v0.6.0-rc0 # copy files into it svn add tvm-0.6.0-rc0 svn ci --username $ASF_USERNAME --password "$ASF_PASSWORD" -m "Add RC"
Call a Vote on the Release Candidate¶
As an incubator project, it requires voting on both dev@ and general@.
The first voting takes place on the Apache TVM (incubator) developers list (firstname.lastname@example.org). To get more attention, one can create a github issue start with “[VOTE]” instead, it will be mirrored to dev@ automatically. Look at past voting threads to see how this proceeds. The email should follow this format.
Provide the link to the draft of the release notes in the email
Provide the link to the release candidate artifacts
Make sure the email is in text format and the links are correct
For the dev@ vote, there must be at least 3 binding +1 votes and more +1 votes than -1 votes. Once the vote is done, you should also send out a summary email with the totals, with a subject that looks something like [VOTE][RESULT] ….
The voting then moves onto the email@example.com. Anyone can contribute a vote, but only “Incubator PMC” (IPMC) votes are binding. To pass, there must be 3 binding +1 votes and more +1 votes than -1 votes.
In ASF, votes are open “at least” 72hrs (3 days). If you don’t get enough number of binding votes within that time, you cannot close the voting deadline. You need to extend it.
Same as the one on dev@, send out a summary email to general@ once the vote passes.
If either voting fails, the community needs to modified the release accordingly, create a new release candidate and re-run the voting process.
Post the Release¶
After the vote passes, to upload the binaries to Apache mirrors, you move the binaries from dev directory (this should be where they are voted) to release directory. This “moving” is the only way you can add stuff to the actual release directory. (Note: only PMC can move to release directory)
export SVN_EDITOR=vim svn mkdir https://dist.apache.org/repos/dist/release/incubator/tvm svn mv https://dist.apache.org/repos/dist/dev/incubator/tvm/tvm-v0.6.0-rc2 https://dist.apache.org/repos/dist/release/incubator/tvm/tvm-v0.6.0 # If you've added your signing key to the KEYS file, also update the release copy. svn co --depth=files "https://dist.apache.org/repos/dist/release/incubator/tvm" svn-tvm curl "https://dist.apache.org/repos/dist/dev/incubator/tvm/KEYS" > svn-tvm/KEYS (cd svn-tvm && svn ci --username $ASF_USERNAME --password "$ASF_PASSWORD" -m"Update KEYS")