Should we continue triaging PRs during the 7th-15 period? Then we stop and only backport what's necessary when the branch is created (i.e. 15th)?
I also want to reiterate the backporting procedure. Xiang was suggesting to create only one PR with all the commits cherry-picked. GIT wise we will always have the same amount of commits, but this could help to pinpoint where all the cherry-picked commits are and come in handy during the next release to separate the backported PR. On Mon, Jun 8, 2020 at 5:20 AM Brennan Ashton <bash...@brennanashton.com> wrote: > > On Wed, Jun 3, 2020 at 2:12 PM Abdelatif Guettouche > <abdelatif.guettou...@gmail.com> wrote: > > Generating release notes is the part that has the most painful work, > > it took 4 of us last time to get it done. I still wonder if there is > > a way to automate that, maybe with good PR summaries and consistent > > labeling. > > Nathan created a confluence page to prepare release notes for the 9.1 > > ahead of time. > > Alright now that we at least have a draft of the release notes for > both the OS and Apps I would propose this timeline: > June 7-15th - Focus on stabilizing and any outstanding features that > we can close out > June 15th - Create the release branch 9.1 and ask for testing on that > branch and refine the release notes > June 22th - Cut RC0 and put it up for a vote to PPMC, if people are > feeling comfortable with the level of testing we can move this up, but > let's really try to get some testing in. > June 25th-27th - (Approximately assuming RC passes) put the RC up for > a vote to IPMC > > I am happy to drive this forward. > > --Brennan
