> I did notice a fair number of patches for bug fixes this week that we may > want to be applying to this release including the spresense and esp, but > there may have been others as well. It would be nice if those could be > backported as needed prior to cutting the RC.
Regarding Xtensa/ESP32, I can backport a couple, but it's better to leave those that add new features for the next release. On Sat, Oct 10, 2020 at 3:09 AM Brennan Ashton <bash...@brennanashton.com> wrote: > > I'm a little behind where I wanted to be but I have collected a bunch of > the boards that we support and am going to work through what I can test > with them this weekend. > > I did notice a fair number of patches for bug fixes this week that we may > want to be applying to this release including the spresense and esp, but > there may have been others as well. It would be nice if those could be > backported as needed prior to cutting the RC. > > --Brennan > > On Sat, Oct 3, 2020, 9:52 PM Brennan Ashton <bash...@brennanashton.com> > wrote: > > > The releases/10.0 branches have been created off of master for both > > apps and the OS. > > > > I will work on populating the release note board tomorrow and starting > > to compile them. > > If any fixes need to be made for the 10.0.0 release they should be > > made against master > > and then a new PR made against the release branch with BACKPORT in the > > title so it > > is easier to identify. > > > > Also this issue was called out as being a blocker: > > https://github.com/apache/incubator-nuttx/issues/1804 > > > > --Brennan > > > > 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 > >
