...
For the dev@ vote, there must be at least 3 +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.
EMAIL TEMPLATE: OPENING A VOTE TO DEV@ 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 pip build: <Link>
Please remember to TEST first before voting accordingly: +1 = approve +0 = no opinion -1 = disapprove (provide reason) |
---|
...
Once each vote is complete, send out a results email.
EMAIL TEMPLATE: VOTING RESULTS To: dev@mxnet.apache.org Subject: [RESULTS] [VOTE] Release MXNet version 0.11.0.RC# This vote passes with 7 +1 votes (3 bindings) and no 0 or -1 votes. +1 votes PMC Members: * $Name * $Name * $Name Committers: * $Name * $Name Community: * $Name * $Name 0 votes * No votes -1 votes * No votes Vote thread: https://lists.apache.org/list.html?commits@mxnet.apache.org/ I'll continue with the release process and the release announcement will follow in the next few days. |
---|
...
EMAIL TEMPLATE: CANCEL A VOTE 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. |
---|
EMAIL TEMPLATE: OPEN A VOTE TO GENERAL@ This is a call for a releasing Apache MXNet #.#.#-incubating, release |
---|
3. Finalizing and posting a release:
...