I created the branch, it's up to date with master. >From now on, we only backport to the branch what we think is necessary to the release.
> We should probably figure out how this patch would be represented in code > and if we want to have 9.0.0-RC1 or whatever supported. What do you mean in code? A release will go through possibly multiple release candidates all tagged as 9.0.0-rcX, the final tag will be the same as the last accepted RC without the -rc suffix. Patches will have to go through the same process. With the voting in the incubator general list, etc. On Mon, Apr 13, 2020 at 12:59 AM Brennan Ashton <bash...@brennanashton.com> wrote: > > On Sun, Apr 12, 2020, 4:55 PM Gregory Nutt <spudan...@gmail.com> wrote: > > > > > > With this in mind and with the suggestion from Brennan, the branch > > > would be "releases/9.0.0" > > > > There there would be tags on the branch to differentiate 9.0.1 from > > 9.0.2? and from release candidates? > > > > So would the branch name releases/9.0 still be OK? The tags on the > > branch would pick up the 3rd digit? I don't really care and I am trying > > to leave the decisions in the hands of the people doing the work. No > > need for bossy spectators; no need for spectators period. But I thought > > I should mention that. > > > > Greg > > > > This all seems very reasonable to me. No need to bikeshed too much, we can > always learn from the release and refine as we go along. > > We should probably figure out how this patch would be represented in code > and if we want to have 9.0.0-RC1 or whatever supported. > > >
