mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ly Nguyen <>
Subject July 2017 Release
Date Tue, 11 Jul 2017 23:07:46 GMT
@mentors, we would like to hold a RC vote and release on Monday July 17th.

   - Are there any blockers (i.e., licenses)?
   - Can you validate the proposal below?

*Start voting THIS week. Release on Monday July 17th.*

   1. Create signing keys
      1. SKIP web of trust linking and upload to public keyserver this time
   2. Create RC in
      1. Currently missing a DISCLAIMER file - do we need that?
      2. SKIP creating SHA checksum this time
   3. Start a vote on dev@ list
   4. svn mv RC to the release location


   - 3 +1 votes from IPMC members (these are the votes that count but we
   should open up to the whole podling community)
   - For podlings, 2 additional constraints:
      - Release artifacts must include “incubating” in final file name (ex:
      - Release artifacts must include disclaimer in the release artifacts

   - The Incubator PMC expects the source releases to be staged on so that
   they can easily be moved to the release location via svn mv   (
   - After graduating, RC’s go into
   and official releases go into

   - Apache Press Team []
   must review and coordinate releases for branding
   - On website and in release DISCLAIMER file:
   - Apache Podling-Name is an effort undergoing incubation at The Apache
      Software Foundation (ASF), sponsored by the name of Apache TLP sponsor.
      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
      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.
      - Website should include Apache Incubator logo:

   - Release should include:
      - LICENSE
      - NOTICE - attribution notices

   - A release must contain source package which is cryptographically
   signed by Release Manager with detached signature. It must be tested prior
   to voting for release.
   - Release must only contain appropriately licensed code
   - Please ensure you wait >=24 hours after uploading a release before
   making announcements so mirrors catch up
   - Releases of more than 1GB of artifacts require a heads-up to
   Infrastructure in advance.
   - Which directory for what build?

   - Artifacts MUST be accompanied by:
      - apache-mxnet-src-0.10.1-incubating.asc - contains OpenPGP
      compatible ASCII armored detached signature
      - apache-mxnet-src-0.10.1-incubating.md5 - MD5 checksum
      - apache-mxnet-src-0.10.1-incubating.sha - SHA checksum (SHOULD)
   - Publish KEYS file in distribution directory root
      - Signing keys MUST be published in KEYS file, SHOULD be available in
      global public keyserver, SHOULD be linked
      into web of trust
      - Keys MUST be RSA & 4096 bits

   - Apache RAT can assist in checking license compliance
   - Eventually we should set up a build system to sign our releases with
   cryptographic signatures. For now we’ll do it manually.

   - Create a signature and sign releases as mentioned above

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message