...

2. Running the voting process for a release:

Step 2.1. Vote on dev@ 

The full voting process is consists of two phases: 3 days on (1) vote on dev@mxnet.apache.org,  (3 days on http://) (2) vote on general@incubator.apache.org (3 days)

Step 2.1. Vote on dev@ 

For the dev@ vote, there must be at least 3 binding +1 votes and more +1 votes than -1 votes. Once that quorum has been reached, the vote then moves onto the general@ vote, where anyone can contribute a vote, but only MXNet PMC votes are binding. To pass, there must be 3 +1 PMC votes and more +1 votes than -1 votes. Send out a notice to vote..

Use the email template below to start the vote:

To: dev@mxnet.apache.org

Subject: [VOTE] Release MXNet version 0.11.0.RC#

This is the vote to release Apache MXNet (incubating) version 0.11.0. Voting will start now and close $utc_now+72.

Link to release notes: <Link>

Link to release candidate 0.11.0.rc0: <Link> 

Link to source and signatures on apache dist server: <Link>

Link to scala packages on the staging repo: <Link>

Please remember to TEST first before voting accordingly:

+1 = approve

+0 = no opinion

-1 = disapprove (provide reason)

...

To: dev@mxnet.apache.org

Subject: [CANCELLED] [VOTE] Release MXNet version 0.11.0.RC#

    We are CANCELLING this vote because...

    We will address this issue and send out RC#+1 for another vote.

Step 2.4. Start a vote on general@

For the vote on general@, anyone can contribute a vote, but only MXNet PMC votes are binding.
To pass, there must be 3 binding +1 votes and more +1 votes than -1 votes.

Send out a notice to vote with the template below.
To get the fingerprint of your keys, run `gpg2 --list-keys --fingerprint`

...