I would prefer that this regression get resolved before we announce the 10.0 release candidate: https://github.com/apache/incubator-nuttx/issues/1804
Thanks Xiang On Fri, Sep 25, 2020 at 12:34 AM Adam Feuer <a...@starcat.io> wrote: > > Alin, > > Thanks, I would love your help on the next release, I'm looking forward to > working together. > > cheers > adam > > > On Wed, Sep 23, 2020 at 11:15 PM Jerpelea, Alin <alin.jerpe...@sony.com> > wrote: > > > HI Brennan, > > > > The release schedule looks god. > > > > @Adam Feuer > > I want to help you on the next release process if you want > > > > Regards > > Alin > > > > > > -----Original Message----- > > From: Adam Feuer <a...@starcat.io> > > Sent: den 23 september 2020 21:13 > > To: dev@nuttx.apache.org > > Subject: Re: [DISCUSS] NuttX 10.0.0 Release schedule > > > > Brennan, > > > > Thanks for doing all this. I'm willing to be release manager for the next > > release after 10.0.0. > > > > -adam > > > > > > On Tue, Sep 22, 2020 at 10:13 PM Brennan Ashton <bash...@brennanashton.com > > > > > wrote: > > > > > Hey all, we have talked in loose terms about this release, but I think > > > it is time we committed, it has been probably too long since our last > > > release. > > > > > > Here is what I would propose for a release schedule: > > > > > > 09/28/20 -- Master Stability Window (keep the merging of risky PRs > > > to a minimum this week) > > > 10/03/20 -- Create the 10.0 release branch > > > 10/04/20 - 10/12/20 -- Stabilize / test / release notes > > > Additionally in this window we need to make a couple CI tweeks to > > > handle the new docs off of the release branch (I expect this won't be > > > much work, but will be easier with the branch in place) > > > 10/12/20 -- Tag RC0 and call for PPMC / Community Vote > > > 10/15/20 (or when we have the votes) Call for IPMC Vote or create a > > > new RC if needed to address issues > > > 10/23/20 (Pending votes and RC0 issues) -- Release RC0 > > > 10/24/20 -- Update site and announce (we have to wait for download > > > mirrors to sync). > > > > > > I know that is almost a month, but that is usually about how long it > > > takes for the whole process, but realistically there is only a week or > > > so where we are aiming to slow down and stabilize the master branch. > > > The rest of it is testing, documenting, voting, and waiting time. > > > > > > I can be the release manager again for this one. But it would be great > > > if someone else jumps in for the release after and I will try to > > > document things a bit more to make the process easier. We will need > > > to have more than one release manage to graduate, there are other > > > projects that have run into this. > > > > > > --Brennan > > > > > > > > > -- > > Adam Feuer <a...@starcat.io> > > > > > -- > Adam Feuer <a...@starcat.io>
