THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Send an email to announce@apache.org, general@incubator.apache.org and dev@mxnet.incubator.apache.org with the subject: [ANNOUNCE] Apache MXNet <release number> Release and a body along the lines of:
| Info | ||
|---|---|---|
|
...
To: announce@apache.org, general@incubator.apache.org, dev@mxnet.incubator.apache.org |
...
(incubating) version $release Dear all, |
...
The Apache MXNet |
...
(incubating) community is happy to announce Apache MXNet (incubating) version |
...
##. |
...
#. |
...
This is our first official release as an incubating Apache project. The project has now fully migrated its codebase and website to Apache.
This release includes code contributions from developers from Apple, Samsung, Microsoft and many other.
We have also crossed over 400 contributors on the project so far. The 0.11.0 release features Apple Core ML model converter, Support for Keras v1.2.2.
ADD A DESCRIPTION! - A Flexible and Efficient Library for Deep Learning
A blog that explains an end to end use case of building an ios app using MXNet and Core ML:
The AWS blog that highlights the key features of the release:
https://aws.amazon.com/blogs/ai/apple-core-ml-and-keras-support-now-available-for-apache-mxnet/
A full list of the changes in this release can be found in the release notes:
https://cwiki.apache.org/confluence/display/MXNET/MXNet+0.11.0+Release+Notes
Link to Download: http://www.apache.org/dist/incubator/mxnet/
To build this project, view this page and select “Build from Source”:
http://mxnet.incubator.apache.org/get_started/install.html
The Docker Images can be found here:
https://hub.docker.com/u/mxnet/
The Pip package can be found here:
https://pypi.python.org/pypi/mxnet
The Release Tag is here:
https://github.com/apache/incubator-mxnet/tree/0.11.0
MXNet Resources
#! ( ## if applicable ## ) Release blog post: ( ## -- if applicable -- ## ) Apache MXNet (incubating) is a deep learning framework designed for both efficiency and flexibility. It allows you to mix symbolic and imperative programming to maximize efficiency and productivity. ( ## for patch releases ## ) 1.3.1 is a maintenance release incorporating important bug fixes and important performance improvements. ( ## -- for patch releases -- ## ) A full list of the changes in this release can be found in the release notes: A link to the download can be found here: If you prefer to build from source and experiment with various compile-time configuration options, use this link to get the instructions: Or You can download and play with MXNet easily using one of the options below: 1. The Pip packages can be found here: 2. The Docker Images can be found here: Links in Maven to the published Scala packages: https://repository.apache.org/content/repositories/releases/org/apache/mxnet/ and to the experimental Clojure packages: https://hub.docker.com/u/mxnet/ The Pip package: https://pypi.python.org/pypi/mxnet The Release Tag: https://github.com/apache/incubator-mxnet/tree/#.#.# MXNet Resources |
...
- Wiki |
...
...
) |
...
For more information |
...
on Apache MXNet (incubating), please see: |
...
Thanks!
...
Best regards, _______ |
...
DISCLAIMER: Apache MXNet (incubating) is an effort undergoing incubation at The |
...
Apache Software Foundation (ASF), sponsored by the name of Apache |
...
Incubator PMC. Incubation is required of all newly accepted |
...
projects until a further review indicates that the |
...
infrastructure, communications, and decision making process have |
...
stabilized in a manner consistent with other successful ASF |
...
projects. While incubation status is not necessarily a reflection |
...
of the completeness or stability of the code, it does indicate |
...
...
that the project has yet to be fully endorsed by the ASF. |
https://cwiki.apache.org/confluence/x/BINjB |
Once the release is complete, make sure that all PRs that were created during the release process only for the release branch (version updates, README NEWS etc) are now merged into the master branch too.
3.7. Bump up the versions on the master
- Merge the PR you created for the release branch into the master
- Add a new PR to update the version to one up/or next release for pip-releases
...