On Sat, May 23, 2020, 8:26 AM Xiang Xiao <xiaoxiang781...@gmail.com> wrote:
> > > > -----Original Message----- > > From: Abdelatif Guettouche <abdelatif.guettou...@gmail.com> > > Sent: Saturday, May 23, 2020 9:18 PM > > To: dev@nuttx.apache.org > > Subject: Re: Release Notes for the NEXT version of NuttX > > > > > Yes, it's better to accumulative all patch for a specific release > candidate in an issue/request in the future release, then we can track > > each release more easier. > > > > Commit wise, we would have the same history, or are you suggesting to > squash all the backported commits? > > > > No, the commit still separate as master, but we use one issue/pr track all > cherry-picked patch for a release candidate. And to help track the history, > only the critical bug fix get cherry-picked from master to release branch. > If you do that with a label then you can set up a GitHub "project" that automatically does this including columns for the state of it. --Brennan >
