I generated the project board for all the OS PRs in this release cycle. I already sorted out a bunch of minor ones, but there are around 1000PRs that came in this cycle. https://github.com/apache/incubator-nuttx/projects/9
Nathan in the past you have created the confluence page to add these to, do you want to do that again? Might be easier if we tweaked it to be in markdown so there is less extra work converting it to markdown later? --Brennan On Thu, Apr 8, 2021 at 10:17 PM <alin.jerpe...@sony.com> wrote: > > Hi all, > > Our 10.1 release branch is live > https://github.com/apache/incubator-nuttx/tree/releases/10.1 > > I propose that we test this branch and backport all fixes until 16 April then > we cut RC0 > > Regards > Alin > > > > -----Original Message----- > From: Brennan Ashton <bash...@brennanashton.com> > Sent: den 5 april 2021 03:50 > To: dev@nuttx.apache.org > Subject: Re: NuttX-10.1 > > On Thu, Apr 1, 2021 at 1:40 PM Abdelatif Guettouche > <abdelatif.guettou...@gmail.com> wrote: > > > > Hi Alin, > > > > There are a few notes here [1] including the pre-Apache release checklist. > > However, for the "pre-release" process, what has been done for earlier > > releases is the following: > > 1. Agree on a date to create the release branches. (I suggest ASAP for > > this one) 2. Keep accepting PRs on master and only backport bugfixes > > to the release branches. (this soak period is usually 1 week) 3. Start > > the release process. > > > > The release process includes creating the release notes, cutting the > > first RC0 and calling for a vote. > > We have [2] for instructions on validating a staged release. > > > > I can try to update the wiki with some of my notes from handling the next few > releases including some email templates. > One thing that I would recommend that you do now is make sure you have a GPG > key ready and add it to this file > https://urldefense.com/v3/__https://downloads.apache.org/incubator/nuttx/KEYS__;!!JmoZiZGBv3RvKRSx!rJgjHuNfNr8PS7UJmpE1p53EgFN0rmYuyQxgu8H9nQprf9w2dt7rWDiczmHvbdvKQg$ > https://urldefense.com/v3/__https://infra.apache.org/release-signing.html*keys-policy__;Iw!!JmoZiZGBv3RvKRSx!rJgjHuNfNr8PS7UJmpE1p53EgFN0rmYuyQxgu8H9nQprf9w2dt7rWDiczmG5hgkVqw$ > > You can find that file in the same SVN repository that is used for uploading > release artifacts. > > If there is anything I can do to help here please let me know. > > > Creating the release notes is what takes most of our time. For the > > past releases working with a Github Project helped a lot and allowed > > us to collaborate effectively. However, Brennan has a tool that > > automates most of this. He used it in the latest release. > > Happy to do this again if you want. I think it does make the whole process a > lot faster. > > --Brennan
