THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
After every release, the community should decide on a list of features to deliver for the following release. When the clear target date for a release has been estimated, the release lead should inform the community of the release schedule. All features which the community wishes to include in the release should be merged and tested successfully before the date of the first release candidate. The first release candidate should be on a commit which passed builds from at least 3 days before cutting the release candidate. This will make the release lead's job easier. Below is a template for the information:
| Code Blockinfo | ||||
|---|---|---|---|---|
| ||||
To: dev@mxnet.apache.org Subject: Release plan - MXNET $release [Announce] Upcoming Apache MXNet (incubating) $release releaseDear MXNet community, Dear MXNet community,I will be the release manager for the upcoming $release release. (Optional: $CO-RM will be co-managing the release and providing help from the committers side.)I am starting the process to prepare for MXNET $release release. I have drafted release notes ($link) to cover the tasks under this release. A release candidate will be cut on $utc_date and voting will commence $utc_date_vote0 - $utc_date_vote1. Release notes have been drafted here [1]. If you have any additional features in progress and would like to include it in this release, please assure they have been merged by $utc_date-72 comment so I may update the release notes.. Feel free to add any other comments/suggestions. Thanks, $RM [1] $release-notes-link |
Step 1.3. Make sure all files have correct License headers and the top level LICENSE file has been updated
...