Re: [DISCUSS] NuttX 10.0.0 Release schedule

2020-10-02 Thread Brennan Ashton
I'm still seeing some important changes outstanding and in flux and no real
stability window what do people think about shifting the schedule by 4
days. So the branch would be created on 10/7 (My evening time GMT-7)
instead of 10/3.  Having to deal with backports right off the bat is not
really gaining us anything and will likely result in a less productive test
window.

--Brennan

On Thu, Oct 1, 2020, 8:56 PM Xiang Xiao  wrote:

> 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  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 
> > 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 
> > > 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 
> > >
> >
> >
> > --
> > Adam Feuer 
>


Re: [DISCUSS] NuttX 10.0.0 Release schedule

2020-10-02 Thread Gregory Nutt




I'm still seeing some important changes outstanding and in flux and no real
stability window what do people think about shifting the schedule by 4
days. So the branch would be created on 10/7 (My evening time GMT-7)
instead of 10/3.  Having to deal with backports right off the bat is not
really gaining us anything and will likely result in a less productive test
window.


Do you think things will be less in flux then?  I doubt that.  I would 
say branch it and bring in only any necessary bug fixes. Any features 
would need to wait for 10.1.


There is no necessity to collect new features at the very tail end of 
the release time.  That is not a good practice either.  It is better to 
let new features mature for the two month time than to release less 
certain features at the least minute.