THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Tag all the dependent submodules for every MXNet release. If a code-change (e.g. bug-fix) is required to a dependent sub-module then we take a branch from the tag and apply the code-change only to the branch for the sub-module so that the change is minimal. This should allow the MXNet release process to have better convergence towards a stable release.
Step 1.10. Create
...
artifacts for the release and push to the dist folder
The src tar - apache-mxnet-src-#.#.#.rc0-incubating.tar.gz:
...
| Info | ||||
|---|---|---|---|---|
| ||||
To: dev@mxnet.apache.org Dear MXNet community, This is the vote to release Apache MXNet (incubating) version $release. Voting will start $start-date-time and close on $end-date-time, $time-zone. Link to release notes: Link to release candidate: Link to source and signatures on apache dist server: Link to scala packages on the staging repo: * CPU * GPU Please remember to TEST first before voting accordingly:
|
Step 2.2.
...
Testing Release Candidate (for Contributors)
There are 3 ways of getting the source code for the release candidate
- Check out tag
Method 1git clone --recursivehttps://github.com/apache/incubator-mxnet.gitgit checkout tags/<tag_name> -b <branch_name>
Method 2git clone --recursivehttps://github.com/apache/incubator-mxnet.git--branch=<tag_name> - Download the zip on Github Source page
https://github.com/apache/incubator-mxnet/tags - Download the distribution
https://dist.apache.org/repos/dist/dev/incubator/mxnet/
Once checked out, follow the steps to build mxnet from source [1] and then various tests can be run.
It is recommended that contributors test out parts of the MXNet codebase they have touched. This ensures greater coverage of the testing and reduces the risk of running into errors post release.
Note: CPU vs GPU, MKLDNN : ON/OFF, Linux vs Centos vs Windows vs Mac are various configurations possible.
Make sure to verify the build flags before running the tests on the release candidate.
[1] https://mxnet.apache.org/get_started/build_from_source
Step 2.3. Send out the vote results on dev@
| Info | ||||
|---|---|---|---|---|
| ||||
| Info | ||||
| ||||
To: dev@mxnet.apache.org I'm happy to announce the results of the vote. This vote passes with <num> +1 votes (<num> binding) and no 0 or -1 votes. +1 votes I'll continue with the release process and the release announcement will follow in the next few days.
[1] https://lists.apache.org/thread.html/<link> |
Step 2.
...
4. Triage issues and re-vote if necessary
Should any vote fail to reach quorum or release lead determines that another RC needs to go out, the release lead should triage the issues, create GitHub issues, and move to fix the issues. Once fixed, make changes to NEWS & README.md in case it specifically lists the old RC# number. Start the process for another release candidate. In the new voting email, detail what has changed since the last release candidate. Repeat until the vote passes.
| Info | ||||
|---|---|---|---|---|
| ||||
To: dev@mxnet.apache.org We are cancelling this vote because: ... We will address the issues and send out rc#+1 for another vote. Best regards, |
Step 2.
...
5. Start a vote on general@
For the vote on general@, 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.
...
| Info | ||||
|---|---|---|---|---|
| ||||
To: general@incubator.apache.org Dear community, This is a call for a releasing Apache MXNet (incubating) #.#.#, release Apache MXNet (incubating) community has voted and approved the release. Vote thread: Result thread: The source tarball, including signatures, digests, etc. can be found at: The tag to be voted upon is #########: The release hash is #########: Release artifacts are signed with the following key: KEYS file available: For information about the contents of this release, see: The vote will be open for 72 hours. [ ] +1 release this package as ######### Best regards, |
Step 2.
...
6: Send out the vote results on general@
Send out an email on general@ in the same voting thread which you sent in previous step to summarize the result.
...