THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The full voting process consists of two phases: (1) vote on dev@mxnet.apache.org (3 days) (2) vote on general@incubator.apache.org (3 days). For full documentation refer to the Apache Voting Process. We should cc the incubation mentors in the vote threads to keep them informed.
Our mentors are: Bob Paulin (bob@apache.org), Henri Yandell (bayard@apache.org), Jason Dai (jasondai@apache.org), Markus Weimer (weimer@apache.org), Michael Wall (mjwall@apache.org).
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.
...
| Info | ||||
|---|---|---|---|---|
| ||||
Cc: mentors 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:
|
...
| Info | ||||
|---|---|---|---|---|
| ||||
Cc: mentors 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> |
...
- Run make html from the docs folder while on your edit branch and make sure the changes look good. At this point you can submit your PR.
- While the PR is clearing CI, you can also test the publish job. This job happens every 6 hours, but it is good to make sure it's going to work once your PR gets merged.
- Run the following from the docs/build_version_doc/ folder, but update it to include the new release's branch and name:
./build_all_version.sh "v1.4.x;v1.3.x;v1.2.0;v1.1.0;v1.0.0;v0.12.0;v0.11.0;master" "1.4.0;1.3.1;1.2.1;1.1.0;1.0.0;0.12.1;0.11.0;master"
- Then run the following to update the html and navigation. Make sure you add the new release version in the first parameter. Also update the last parameter to be the public IP of your staging web server. Publish the output of docs/build_version_doc/VersionedWeb to your staging server. For more details refer to building the production website.
./update_all_version.sh "1.4.0;1.3.1;1.2.1;1.1.0;1.0.0;0.12.1;0.11.0;master" master http://34.201.8.176/
...