You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Matteo Merli <mm...@apache.org> on 2023/02/17 22:44:34 UTC
[PROPOSAL] Roadmap for 3.0 release
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
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
<mm...@apache.org>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by "rxl@apache.org" <ra...@gmail.com>.
+1
--
Thanks
Xiaolong Ran
Yubiao Feng <yu...@streamnative.io.invalid> 于2023年3月3日周五 14:38写道：
> The same as Zike (^_^)
>
> Thanks to Matteo for initiating this release roadmap. I am interested in
> this release. I'd also like to volunteer as a release manager for Apache
> Pulsar 3.0.0
>
> Thanks
> Yubiao Feng
>
> On Sat, Feb 18, 2023 at 6:44 AM Matteo Merli <mm...@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
> >
> > 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
> > <mm...@apache.org>
> >
>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Yubiao Feng <yu...@streamnative.io.INVALID>.
The same as Zike (^_^)
Thanks to Matteo for initiating this release roadmap. I am interested in
this release. I'd also like to volunteer as a release manager for Apache
Pulsar 3.0.0
Thanks
Yubiao Feng
On Sat, Feb 18, 2023 at 6:44 AM Matteo Merli <mm...@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
>
> 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
> <mm...@apache.org>
>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Cong Zhao <zh...@apache.org>.
+1 Looks great!
Thanks,
Cong
On 2023/02/17 22:44:34 Matteo Merli 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
>
> 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
> <mm...@apache.org>
>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Zike Yang <zi...@apache.org>.
Hi,
Thanks to Matteo for initiating this release roadmap. I am interested
in this release.
I'd also like to volunteer as a release manager for Apache Pulsar 3.0.0.
Thanks,
Zike Yang
On Tue, Feb 21, 2023 at 10:56 PM tison <wa...@gmail.com> wrote:
>
> +1
>
> Thanks for driving this effort!
>
> Also, I created https://github.com/apache/pulsar/issues/19570 to
> correspondingly update our website. Feel free to leave a comment. I'm going
> to send a draft in days.
>
> Best,
> tison.
>
>
> Enrico Olivelli <eo...@gmail.com> 于2023年2月21日周二 19:20写道：
>
> > +1
> >
> > Perfect
> >
> > Enrico
> >
> > Il giorno mar 21 feb 2023 alle ore 08:11 Haiting Jiang
> > <ji...@gmail.com> ha scritto:
> > >
> > > +1 Looks great!
> > >
> > >
> > > Haiting
> > >
> > > On Tue, Feb 21, 2023 at 12:11 PM Hang Chen <ch...@apache.org> wrote:
> > > >
> > > > +1
> > > >
> > > > Thanks,
> > > > Hang
> > > >
> > > > Christophe Bornet <bo...@gmail.com> 于2023年2月20日周一 21:46写道：
> > > > >
> > > > > +1
> > > > >
> > > > > Also, I'd like to volunteer as a release manager for this release.
> > > > >
> > > > > Christophe
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Le ven. 17 févr. 2023 à 23:44, Matteo Merli <mm...@apache.org> a
> > écrit :
> > > > > >
> > > > > > 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
> > > > > >
> > > > > > 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
> > > > > > <mm...@apache.org>
> >
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by tison <wa...@gmail.com>.
+1
Thanks for driving this effort!
Also, I created https://github.com/apache/pulsar/issues/19570 to
correspondingly update our website. Feel free to leave a comment. I'm going
to send a draft in days.
Best,
tison.
Enrico Olivelli <eo...@gmail.com> 于2023年2月21日周二 19:20写道：
> +1
>
> Perfect
>
> Enrico
>
> Il giorno mar 21 feb 2023 alle ore 08:11 Haiting Jiang
> <ji...@gmail.com> ha scritto:
> >
> > +1 Looks great!
> >
> >
> > Haiting
> >
> > On Tue, Feb 21, 2023 at 12:11 PM Hang Chen <ch...@apache.org> wrote:
> > >
> > > +1
> > >
> > > Thanks,
> > > Hang
> > >
> > > Christophe Bornet <bo...@gmail.com> 于2023年2月20日周一 21:46写道：
> > > >
> > > > +1
> > > >
> > > > Also, I'd like to volunteer as a release manager for this release.
> > > >
> > > > Christophe
> > > >
> > > >
> > > >
> > > >
> > > > Le ven. 17 févr. 2023 à 23:44, Matteo Merli <mm...@apache.org> a
> écrit :
> > > > >
> > > > > 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
> > > > >
> > > > > 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
> > > > > <mm...@apache.org>
>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Enrico Olivelli <eo...@gmail.com>.
+1
Perfect
Enrico
Il giorno mar 21 feb 2023 alle ore 08:11 Haiting Jiang
<ji...@gmail.com> ha scritto:
>
> +1 Looks great!
>
>
> Haiting
>
> On Tue, Feb 21, 2023 at 12:11 PM Hang Chen <ch...@apache.org> wrote:
> >
> > +1
> >
> > Thanks,
> > Hang
> >
> > Christophe Bornet <bo...@gmail.com> 于2023年2月20日周一 21:46写道：
> > >
> > > +1
> > >
> > > Also, I'd like to volunteer as a release manager for this release.
> > >
> > > Christophe
> > >
> > >
> > >
> > >
> > > Le ven. 17 févr. 2023 à 23:44, Matteo Merli <mm...@apache.org> a écrit :
> > > >
> > > > 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
> > > >
> > > > 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
> > > > <mm...@apache.org>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Haiting Jiang <ji...@gmail.com>.
+1 Looks great!
Haiting
On Tue, Feb 21, 2023 at 12:11 PM Hang Chen <ch...@apache.org> wrote:
>
> +1
>
> Thanks,
> Hang
>
> Christophe Bornet <bo...@gmail.com> 于2023年2月20日周一 21:46写道：
> >
> > +1
> >
> > Also, I'd like to volunteer as a release manager for this release.
> >
> > Christophe
> >
> >
> >
> >
> > Le ven. 17 févr. 2023 à 23:44, Matteo Merli <mm...@apache.org> a écrit :
> > >
> > > 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
> > >
> > > 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
> > > <mm...@apache.org>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Hang Chen <ch...@apache.org>.
+1
Thanks,
Hang
Christophe Bornet <bo...@gmail.com> 于2023年2月20日周一 21:46写道：
>
> +1
>
> Also, I'd like to volunteer as a release manager for this release.
>
> Christophe
>
>
>
>
> Le ven. 17 févr. 2023 à 23:44, Matteo Merli <mm...@apache.org> a écrit :
> >
> > 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
> >
> > 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
> > <mm...@apache.org>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Christophe Bornet <bo...@gmail.com>.
+1
Also, I'd like to volunteer as a release manager for this release.
Christophe
Le ven. 17 févr. 2023 à 23:44, Matteo Merli <mm...@apache.org> a écrit :
>
> 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
>
> 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
> <mm...@apache.org>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Zike Yang <zi...@apache.org>.
+1
Zike Yang
On Sat, Feb 18, 2023 at 4:43 PM <ma...@gmail.com> wrote:
>
> +1
> On Feb 18, 2023, 14:56 +0800, Michael Marshall <mm...@apache.org>, wrote:
> > +1 - this timeline sounds even better :)
> >
> > On Sat, Feb 18, 2023 at 12:41 AM Matteo Merli <ma...@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
> > > <ma...@gmail.com>
> > >
> > >
> > > On Fri, Feb 17, 2023 at 10:39 PM Dave Fisher <wa...@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 <mm...@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
> > > > > > > <mm...@apache.org>
> > > > >
> > > > >
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by ma...@gmail.com.
+1
On Feb 18, 2023, 14:56 +0800, Michael Marshall <mm...@apache.org>, wrote:
> +1 - this timeline sounds even better :)
>
> On Sat, Feb 18, 2023 at 12:41 AM Matteo Merli <ma...@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
> > <ma...@gmail.com>
> >
> >
> > On Fri, Feb 17, 2023 at 10:39 PM Dave Fisher <wa...@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 <mm...@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
> > > > > > <mm...@apache.org>
> > > >
> > > >
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Michael Marshall <mm...@apache.org>.
+1 - this timeline sounds even better :)
On Sat, Feb 18, 2023 at 12:41 AM Matteo Merli <ma...@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
> <ma...@gmail.com>
>
>
> On Fri, Feb 17, 2023 at 10:39 PM Dave Fisher <wa...@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 <mm...@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
> > > <mm...@apache.org>
> >
> >
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Matteo Merli <ma...@gmail.com>.
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
<ma...@gmail.com>
On Fri, Feb 17, 2023 at 10:39 PM Dave Fisher <wa...@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 <mm...@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
> > <mm...@apache.org>
>
>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Dave Fisher <wa...@comcast.net>.
+1.
I think that there is a typo. See below.
Sent from my iPhone
> On Feb 17, 2023, at 2:44 PM, Matteo Merli <mm...@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
> <mm...@apache.org>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Zixuan Liu <no...@gmail.com>.
+1 awesome plan.
Thanks,
Zixuan
Michael Marshall <mm...@apache.org> 于2023年2月18日周六 14:33写道：
> +1 I support this timeline.
>
> > I also wanted to propose trying out a model where we have 3 release
> > managers for all major releases.
>
> Great idea, this will be a valuable improvement to our release
> process. It also creates an opportunity for new committers to ease
> into the release management role.
>
> Thanks,
> Michael
>
> On Fri, Feb 17, 2023 at 4:44 PM Matteo Merli <mm...@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
> >
> > 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
> > <mm...@apache.org>
>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Michael Marshall <mm...@apache.org>.
+1 I support this timeline.
> I also wanted to propose trying out a model where we have 3 release
> managers for all major releases.
Great idea, this will be a valuable improvement to our release
process. It also creates an opportunity for new committers to ease
into the release management role.
Thanks,
Michael
On Fri, Feb 17, 2023 at 4:44 PM Matteo Merli <mm...@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
>
> 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
> <mm...@apache.org>
Re: [PROPOSAL] Roadmap for 3.0 release
Posted by Cong Zhao <zh...@apache.org>.
+1 Looks great!
Thanks,
Cong
> 2023年2月18日 06:44，Matteo Merli <mm...@apache.org> 写道：
>
> 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
>
> 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
> <mm...@apache.org>