+1 (binding)

On 01.12.2017 04:30, Chris Olivier wrote:
+1

Additional note:

This MXNet v1.0 release is planned to be announced at the NIPS conference
starting Monday, 04-Dec and hence would request your support in meeting
this timeline. We will continue to address any non-critical issues after
this release as well.

On Thu, Nov 30, 2017 at 4:45 PM, Chris Olivier <cjolivie...@apache.org>
wrote:


Hello All,


This is a call for releasing Apache MXNet (incubating) 1.0.0, release
candidate 1.


Apache MXNet community has voted and approved the release.


*Vote thread:*

https://lists.apache.org/thread.html/568bf0c9960f14640b753a5
fb6766c7b0074339d286f405c04ffec96@%3Cdev.mxnet.apache.org%3E


*Result thread:*

https://lists.apache.org/thread.html/558a60f4d0c16b0311c96af
d059082ebde0f773c56a03cb9e00bc19f@%3Cdev.mxnet.apache.org%3E


*The source tarball, including signatures, digests, etc. can be found at:*

https://dist.apache.org/repos/dist/dev/incubator/mxnet/1.0.0.rc1/



*The release tag can be found here: *

https://github.com/apache/incubator-mxnet/tree/1.0.0.rc1



*The release hash is *25720d0e3c29232a37e2650f3ba3a2454f9367bb* and can
be found here:*

<https://github.com/apache/incubator-mxnet/commit/25720d0e3c
29232a37e2650f3ba3a2454f9367bb>



*Release artifacts are signed with the following key:*

16DD B2E2 FE0C 3925 CB13  38D7 21F3 F9AB C622 DF82



*KEY files are available here:*

https://dist.apache.org/repos/dist/dev/incubator/mxnet/KEYS



*For information about the contents of this release, see:*

<https://cwiki.apache.org/confluence/display/MXNET/Apache+
MXNet+%28incubating%29+1.0+Release+Notes>



The vote will be open for at least 72 hours.


[ ] +1 Release this package as 1.0.0

[ ] +0 no opinion

[ ] -1 Do not release this package because...


Thanks,


-Chris Olivier

cjolivie...@apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to