You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mxnet.apache.org by Meghna Baijal <me...@gmail.com> on 2017/11/07 20:08:10 UTC
The process for a patch release
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
Re: The process for a patch release
Posted by Chris Olivier <cj...@gmail.com>.
Thank you for the clarification! The security release process certainly
makes sense (not to publicly announce security holes).
On Tue, Nov 7, 2017 at 9:41 PM Hen <ba...@apache.org> wrote:
> Yes. You would just do it quicker (if such was truly needed). You would
> still need at least 3 +1s, and at the moment there is the crutch that you
> would also need 3 Incubator PMC +1s (or the first 3 would have to be IPMC).
>
> If it's a security vulnerability, then we would use private@ and confer
> with security@ on the process.
>
> Hen
>
> On Tue, Nov 7, 2017 at 1:45 PM, Chris Olivier <cj...@gmail.com>
> wrote:
>
> > 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
> > >
> >
>
Re: The process for a patch release
Posted by Hen <ba...@apache.org>.
Yes. You would just do it quicker (if such was truly needed). You would
still need at least 3 +1s, and at the moment there is the crutch that you
would also need 3 Incubator PMC +1s (or the first 3 would have to be IPMC).
If it's a security vulnerability, then we would use private@ and confer
with security@ on the process.
Hen
On Tue, Nov 7, 2017 at 1:45 PM, Chris Olivier <cj...@gmail.com> wrote:
> 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
> >
>
Re: The process for a patch release
Posted by Chris Olivier <cj...@gmail.com>.
Do we need a vote for a critical patch release?
On Tue, Nov 7, 2017 at 12:08 PM, Meghna Baijal <me...@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
>
Re: The process for a patch release
Posted by Chris Olivier <cj...@gmail.com>.
I don’t recall where I heard that. Oh well, no worries. Vote it is.
On Tue, Nov 7, 2017 at 5:28 PM Hen <ba...@apache.org> wrote:
> I thought a patch release was exactly the same as a full release; except
> that there is less discussion of the features involved.
>
> Did you see a more lightweight release process described somewhere? I'd
> expect an RC and vote.
>
> Hen
>
> 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
> >
>
Re: The process for a patch release
Posted by Hen <ba...@apache.org>.
I thought a patch release was exactly the same as a full release; except
that there is less discussion of the features involved.
Did you see a more lightweight release process described somewhere? I'd
expect an RC and vote.
Hen
On Tue, Nov 7, 2017 at 12:08 PM, Meghna Baijal <me...@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
>