+1 - this timeline sounds even better :)
On Sat, Feb 18, 2023 at 12:41 AM Matteo Merli <matteo.me...@gmail.com> wrote: > > Ups, > > I started from the release date I was meaning April for the RCs: > > * Tue - 2023-04-11 > * Tue - 2023-04-18 - RC-2 > * Tue - 2023-04-25 - RC-3 > * Tue - 2023-05-02 - Announce 3.0 Release > > Sorry for the mixup! > > -- > Matteo Merli > <matteo.me...@gmail.com> > > > On Fri, Feb 17, 2023 at 10:39 PM Dave Fisher <wave4d...@comcast.net> wrote: > > > +1. > > > > I think that there is a typo. See below. > > > > Sent from my iPhone > > > > > On Feb 17, 2023, at 2:44 PM, Matteo Merli <mme...@apache.org> wrote: > > > > > > Since the LTS release model has been formally approved, I'm proposing > > > the following schedule for the release: > > > > > > * Tue - 2023-05-11 > > > - RC-1 > > > - Code Freeze -- Only critical fixes will be merged in the 3.0 > > > release branch. Contributors should plan to have all the changes merged > > in > > > before this date. Exceptions should be extremely rare and strongly > > > motivated. > > > > > > * Tue - 2023-05-18 - RC-2 > > > * Tue - 2023-05-25 - RC-3 > > > * Tue - 2023-05-02 - Announce 3.0 Release > > > > You meant June 2, 2023? > > > > Best, > > Dave > > > > > > These dates will be published on the website to present users with a > > > "roadmap" and we should commit to and respect these dates. > > > > > > I also wanted to propose trying out a model where we have 3 release > > > managers for all major releases. > > > > > > The reasoning behind this is for this small group of people to > > collaborate > > > and divide the tasks for the release: merging patches from the "master" > > > branch, preparing RC, and testing. > > > > > > Since everyone also has other work duties and unexpected tasks that can > > pop > > > up at any time, it will help to have redundancy in the release-management > > > "team", so that we can release on the exact dates. > > > > > > Thanks, > > > Matteo > > > > > > -- > > > Matteo Merli > > > <mme...@apache.org> > > > >
