...

This produces a CHANGES.txt.new that should be a superset of the existing CHANGES.txt. Replace the old CHANGES.txt with the new one (TODO see this example commit).

Branch creation announcement template

To: dev@mxnet.apache.org
Subject: New release branch 0.10.0

Hello MXNet developers and friends,

As promised, we now have a release branch for 0.10.0 release (with 0.10.0.0
as the version).
Trunk has been bumped to 0.10.1.0-SNAPSHOT.

I'll be going over the github issues to move every non-blocker from this release to
the next release.

From this point, most changes should go to trunk.
*Blockers (existing and new that we discover while testing the release) will be double-committed. 

*Please discuss with your reviewer whether your PR should go to trunk or to trunk+release so they can merge accordingly.

*Please help us test the release! *

Thanks!

$RM

Cutting a Release Candidate

...

• Make a shortened link to the full list of github issues using https://s.apache.org/
• If possible, attach a draft of the release notes with the email
• Make sure the voting closing time is in UTC format. Use this script to generate it - TODO
• Make sure the email is in text format and the links are correct
• RM must have gpg keys with the public key publicly available to validate the authenticity of the Apache MXNet release: If you haven't set up gpg key, set up one using 4096 bit RSA (http://www.apache.org/dev/release-signing.html). Make sure that your public key is uploaded to one of the public servers (http://www.apache.org/dev/release-signing.html#keyserver). Also, add your public key to https://github.com/apache/mxnet-site/blob/asf-site/KEYS

Voting template:

To: dev@mxnet.apache.org
Subject: [VOTE] Release plan - MXNET 0.11

We are starting the process to prepare for MXNET $release release. I have created release plan ($link) to cover the tasks under this release.

If you have any tasks in progress and would like to include it in this release, please follow the process to do so.

Feel free to comment on the github if you have any comments/suggestions.

Thanks,
$RM

Once the vote is done, you should also send out a summary email with the totals, with a subject that looks something like [RESULT] [VOTE]....

Finalize the Release

Be Careful!

...