+1 Looks great!
Thanks,
Cong
> 2023年2月18日 06:44，Matteo Merli 写道：
>
> 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
> rele
+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.
+1
--
Thanks
Xiaolong Ran
Yubiao Feng 于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
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 wrote:
> Since the LTS release model has been fo
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 wrote:
>
> +1
>
> Thanks for driving this effort!
>
> Also, I created htt
+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 于2023年2月21日周二 19:20写道：
> +1
>
> Perfect
>
> Enrico
>
> Il gior
+1
Perfect
Enrico
Il giorno mar 21 feb 2023 alle ore 08:11 Haiting Jiang
ha scritto:
>
> +1 Looks great!
>
>
> Haiting
>
> On Tue, Feb 21, 2023 at 12:11 PM Hang Chen wrote:
> >
> > +1
> >
> > Thanks,
> > Hang
> >
> > Christophe Bornet 于2023年2月20日周一 21:46写道：
> > >
> > > +1
> > >
> > > Also, I'
+1 Looks great!
Haiting
On Tue, Feb 21, 2023 at 12:11 PM Hang Chen wrote:
>
> +1
>
> Thanks,
> Hang
>
> Christophe Bornet 于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 à
+1
Thanks,
Hang
Christophe Bornet 于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 a écrit :
> >
> > Since the LTS release model has been formally approved, I'm proposing
> >
+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 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
>
+1
Zike Yang
On Sat, Feb 18, 2023 at 4:43 PM wrote:
>
> +1
> On Feb 18, 2023, 14:56 +0800, Michael Marshall , wrote:
> > +1 - this timeline sounds even better :)
> >
> > On Sat, Feb 18, 2023 at 12:41 AM Matteo Merli
> > wrote:
> > >
> > > Ups,
> > >
> > > I started from the release date I was
+1
On Feb 18, 2023, 14:56 +0800, Michael Marshall , wrote:
> +1 - this timeline sounds even better :)
>
> On Sat, Feb 18, 2023 at 12:41 AM Matteo Merli wrote:
> >
> > Ups,
> >
> > I started from the release date I was meaning April for the RCs:
> >
> > * Tue - 2023-04-11
> > * Tue - 2023-04-18 - R
+1 - this timeline sounds even better :)
On Sat, Feb 18, 2023 at 12:41 AM Matteo Merli 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 Releas
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
On Fri, Feb 17, 2023 at 10:39 PM Dave Fisher wrote:
> +1.
>
> I th
+1.
I think that there is a typo. See below.
Sent from my iPhone
> On Feb 17, 2023, at 2:44 PM, 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
+1 awesome plan.
Thanks,
Zixuan
Michael Marshall 于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 a
+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.
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 th
18 matches
Mail list logo
