[ANNOUNCE] Apache MXNet (incubating) 1.2.0 Release
Hello all, The Apache MXNet (incubating) Community announces the availability of Apache MXNet (incubating) 1.2.0! Blog: https://medium.com/apache-mxnet/announcing-apache-mxnet-1-2-0-d94f56da154b 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. This release improves usability, performance and interoperability. A full list of the changes in this release can be found in the release notes: https://cwiki.apache.org/confluence/display/MXNET/Apache+MXNet+%28incubating%29+1.2.0+Release+Notes A Link to the Download is here: https://www.apache.org/dyn/closer.cgi/incubator/mxnet/1.2.0 If you prefer to build from source and experiment with various compile-time configuration options, use this link to get the instructions: http://mxnet.incubator.apache.org/install/index.html Or You can download and play with MXNet easily using one of the options below: 1. The Pip package can be found here: https://pypi.python.org/pypi/mxnet 2. The Docker Images can be found here: https://hub.docker.com/r/mxnet/python/ The release tag used for the 1.2.0 release is: https://github.com/apache/incubator-mxnet/tree/1.2.0 Some more MXNet Resources: 1. Issues: https://github.com/apache/incubator-mxnet/issues 2. Wiki: https://cwiki.apache.org/confluence/display/MXNET If you want to learn more about MXNet visit http://mxnet.incubator.apache.org/ Finally, you are welcome to join and also invite your friends to the dynamic and growing MXNet community by subscribing to dev@mxnet.incubator.apache.org Thanks! Apache MXNet (incubating) Team ___ 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.
Permission to delete tasks on MXNET Jira
Hello, I recently created a few tasks (Task MXNET-461 to MXNET-469) in the MXNet Jira page ( https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=211&projectKey=MXNET). It was intended to be created as a subtask under MXNET-425. I do not have permission to change the status of these tasks or to delete them. Could someone convert these tasks to subtasks or delete them? Best, Alex
Re: Introduction of restricted slaves and jobs
Thanks Marco, this is a welcome improvement. On Fri, May 25, 2018, 05:56 Marco de Abreu wrote: > Hello MXNet community, > > I'd like to announce the launch of restricted slaves and jobs for our CI > system. > > The purpose of this feature is to allow separating slaves that execute > arbitrary code from verified code like on our version-branches and the > master. This step is necessary in order to increase the security of > produced artefacts. > > Until now, the generation of user-facing artefacts like our website was run > on the same instances as unverified code from Pull Requests. This could > potentially have been abused to deploy a virus on our slaves (although they > are recycled very frequently through the auto scaling system) that alters > the artefact generation processes and attaches malicious code to it. > > In order to mitigate this attack vector, we're introducing restricted > slaves and jobs. From now on, any user-facing output like nightly builds or > the website, will have to be generated on slaves that are only executing > code that has been verified by our committers by merging the changes into > one of our branches. > > I'd like to invite everybody to review the documentation at > https://cwiki.apache.org/confluence/display/MXNET/Restricted+jobs+and+nodes > . > Considering this is a security feature, I'd especially love to hear > critical input or any ideas that would allow to poke holes into my > solution. > > Best regards, > Marco >
Introduction of restricted slaves and jobs
Hello MXNet community, I'd like to announce the launch of restricted slaves and jobs for our CI system. The purpose of this feature is to allow separating slaves that execute arbitrary code from verified code like on our version-branches and the master. This step is necessary in order to increase the security of produced artefacts. Until now, the generation of user-facing artefacts like our website was run on the same instances as unverified code from Pull Requests. This could potentially have been abused to deploy a virus on our slaves (although they are recycled very frequently through the auto scaling system) that alters the artefact generation processes and attaches malicious code to it. In order to mitigate this attack vector, we're introducing restricted slaves and jobs. From now on, any user-facing output like nightly builds or the website, will have to be generated on slaves that are only executing code that has been verified by our committers by merging the changes into one of our branches. I'd like to invite everybody to review the documentation at https://cwiki.apache.org/confluence/display/MXNET/Restricted+jobs+and+nodes. Considering this is a security feature, I'd especially love to hear critical input or any ideas that would allow to poke holes into my solution. Best regards, Marco
Re: Slack. Subscription
Rahul, I haven't received an email with your invite. On Fri, May 25, 2018 at 9:52 AM, Rahul Huilgol wrote: > Sent an invite! > > On Thu, May 24, 2018, 11:49 PM Ivan Serdyuk > wrote: > > > Please subscribe to the Slack channel. Tnx > > >
