Sorry, late response, please take a look at the previous reply. If you have
good ideas, we could start a discussion.
On 2022/01/05 18:31:38 Michael Marshall wrote:
> +1 - thanks for starting this thread.
>
> >171 commits?
> > Why?
> > This is too much in my opinion for a point release.
>
> I ag
Thanks for your reminder.
Currently, the new added PR will be added the label `branch-x.x`, the label
indicate the PR should be added to which branch. After the PR is merged, the PR
will be cherry-picked to the specific branch. After cherry-pick, a label
`cherry-picked/branch-x.x` will be added
+1
Regards
Jiwei Guo (Tboy)
On Thu, Jan 6, 2022 at 2:32 AM Michael Marshall
wrote:
> +1 - thanks for starting this thread.
>
> >171 commits?
> > Why?
> > This is too much in my opinion for a point release.
>
> I agree that this is a lot of commits, and especially since we only
> just released
+1 - thanks for starting this thread.
>171 commits?
> Why?
> This is too much in my opinion for a point release.
I agree that this is a lot of commits, and especially since we only
just released 2.9.1. Note though that this is not a new phenomenon:
2.8.2 had 251 commits on top of 2.8.1. [0]
> Ev
BTW +1
I hope we will review carefully what we are including in the release
And that we will let branch-2.9 stabilise by not adding any other commits
that are not strictly required:
- security related issues
- data loss/data corruption cases
Enrico
Thank you Ran Gao for starting this thread.
171 commits?
Why?
This is too much in my opinion for a point release.
I am pretty sure that we don't need all that changes.
Every change we cherry pick has a good chance to break the stability
Enrico
Il Mer 5 Gen 2022, 16:30 mattison chao ha scritto:
> +1
>
> regards,
> Mattisonchao
>
> On
+1
regards,
Mattisonchao
On Wed, 5 Jan 2022 at 23:04, Lan Liang wrote:
> +1,Thanks for your work.
>
>
>
>
>
>
> Best Regards,
> Lan Liang
> On 1/5/2022 23:01，Hang Chen wrote：
> +1
>
> Best,
> Hang
>
> 陳智弘 于2022年1月5日周三 21:30写道：
>
> +1
>
> Lari Hotari 於 2022年1月5日 週三 20:56 寫道：
>
> +1
>
> On Wed,
+1,Thanks for your work.
Best Regards,
Lan Liang
On 1/5/2022 23:01，Hang Chen wrote：
+1
Best,
Hang
陳智弘 于2022年1月5日周三 21:30写道：
+1
Lari Hotari 於 2022年1月5日 週三 20:56 寫道：
+1
On Wed, Jan 5, 2022 at 11:23 AM Ran Gao wrote:
Hello, Pulsar community:
I'd like to propose that we release Apache
+1
Best,
Hang
陳智弘 于2022年1月5日周三 21:30写道：
>
> +1
>
> Lari Hotari 於 2022年1月5日 週三 20:56 寫道：
>
> > +1
> >
> > On Wed, Jan 5, 2022 at 11:23 AM Ran Gao wrote:
> >
> > > Hello, Pulsar community:
> > >
> > > I'd like to propose that we release Apache Pulsar 2.9.2.
> > >
> > > Currently, compared to 2.9
+1
Lari Hotari 於 2022年1月5日 週三 20:56 寫道：
> +1
>
> On Wed, Jan 5, 2022 at 11:23 AM Ran Gao wrote:
>
> > Hello, Pulsar community:
> >
> > I'd like to propose that we release Apache Pulsar 2.9.2.
> >
> > Currently, compared to 2.9.1, branch-2.9 already merged 171 commits(refer
> > to [0]), they con
+1
On Wed, Jan 5, 2022 at 11:23 AM Ran Gao wrote:
> Hello, Pulsar community:
>
> I'd like to propose that we release Apache Pulsar 2.9.2.
>
> Currently, compared to 2.9.1, branch-2.9 already merged 171 commits(refer
> to [0]), they contain the log4j security patch and many important fixes.
>
> I
+1
Thanks,
Penghui
On Wed, Jan 5, 2022 at 5:23 PM Ran Gao wrote:
> Hello, Pulsar community:
>
> I'd like to propose that we release Apache Pulsar 2.9.2.
>
> Currently, compared to 2.9.1, branch-2.9 already merged 171 commits(refer
> to [0]), they contain the log4j security patch and many import
Hello, Pulsar community:
I'd like to propose that we release Apache Pulsar 2.9.2.
Currently, compared to 2.9.1, branch-2.9 already merged 171 commits(refer
to [0]), they contain the log4j security patch and many important fixes.
I am happy to volunteer to be the release manager.
I see 4 merged
13 matches
Mail list logo
