Mailing-List: contact dev-help@mxnet.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mxnet.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAMGgKDA03FaS4jkwtzuGYDkotpkZFGoo+tkdFFj6rbo3TwkRxw@mail.gmail.com>
References: <CAMGgKDA03FaS4jkwtzuGYDkotpkZFGoo+tkdFFj6rbo3TwkRxw@mail.gmail.com>
From: Chris Olivier <cjolivier01@gmail.com>
Date: Tue, 7 Nov 2017 13:45:27 -0800
Message-ID: <CABgAAfcPhbGUzDVUAVdWuOLTckST6yScM-=XRwFN2aE_BN64dQ@mail.gmail.com>
Subject: Re: The process for a patch release
To: dev@mxnet.incubator.apache.org
Cc: dev@mxnet.apache.org
Content-Type: multipart/alternative; boundary="089e0825e94049a847055d6b7d7d"
archived-at: Wed, 08 Nov 2017 01:14:47 -0000

--089e0825e94049a847055d6b7d7d
Content-Type: text/plain; charset="UTF-8"

Do we need a vote for a critical patch release?

On Tue, Nov 7, 2017 at 12:08 PM, Meghna Baijal <meghnabaijal2017@gmail.com>
wrote:

> Hi All,
> A patch release is being planned for Apache MXNet(incubating) to include
> some important bug fixes.
> I want to confirm that for a patch release, there is no RC and voting step.
>
> Effectively the process looks something like this -
>
> Step 1: Cherrypick all the necessary bugfixes into the existing release
> branch.
>
> Step 2: Add a PR to update the version number etc (Example
> https://github.com/apache/incubator-mxnet/commit/
> e0c7906693f0c79b0ce34a4d777c26a6bf1903c1
> )
>
> Step 3: Make sure the release branch build passes on builds.apache.jenkins
> and nightly tests
>
> Step 4: tag the release branch in GitHub with the release tag - example
> 0.12.1
>
> Step 5: Download from the repo and checkout the tag, package it and Sign
> the src code into 'apache-mxnet-src-0.12.1-incubating'
>
> Step 6: Validate the signatures and test
>
> Step 7: Update the website. (pip and docker release)
>
> Step 8: Upload the src tar to the final destination -
> http://www.apache.org/dist/incubator/mxnet/
>
> Step 9: Announce the patch release
>
> Thanks,
> Meghna Baijal
>

--089e0825e94049a847055d6b7d7d--