Re: [DISCUSS] BookKeeper 4.15.2 release

2022-09-21 Thread Yong Zhang
I have cherry-picked the PRs to branch-4.15. Please help to check if there has other PRs you want to include in this release. https://github.com/apache/bookkeeper/pulls?q=is%3Apr+label%3Arelease%2F4.15.2+is%3Aclosed If there has no other PRs, I will start releasing tomorrow. Thanks, Yong On Wed

Re: [DISCUSS] BookKeeper 4.15.2 release

2022-09-21 Thread lin chen
+1 发自我的iPhone > 在 2022年9月20日,上午10:47,Yong Zhang 写道: > > I haven't cherry-picked the PRs to branch-4.15. If you have PR wants > to in the next release, you can label it with release/4.15.2 > >> On Mon, 19 Sept 2022 at 15:41, steven lu wrote: >> >> Good idea +1 >> >> Yong Zhang 于2022年9月19日

Re: [DISCUSS] BookKeeper 4.15.2 release

2022-09-19 Thread Yong Zhang
I haven't cherry-picked the PRs to branch-4.15. If you have PR wants to in the next release, you can label it with release/4.15.2 On Mon, 19 Sept 2022 at 15:41, steven lu wrote: > Good idea +1 > > Yong Zhang 于2022年9月19日周一 13:36写道: > > > Hi everyone, > > > > I want to discuss starting 4.15.2 re

Re: [DISCUSS] BookKeeper 4.15.2 release

2022-09-19 Thread steven lu
Good idea +1 Yong Zhang 于2022年9月19日周一 13:36写道: > Hi everyone, > > I want to discuss starting 4.15.2 release to resolve the regression > mentioned here: > https://lists.apache.org/thread/d9gm50kysgjcpbq448s2sy822kho6z6k > > Although it is an unexpected setting caused, we never know how the users

Re: [DISCUSS] BookKeeper 4.15.2 release

2022-09-18 Thread Enrico Olivelli
Il giorno lun 19 set 2022 alle ore 07:36 Yong Zhang ha scritto: > > Hi everyone, > > I want to discuss starting 4.15.2 release to resolve the regression > mentioned here: > https://lists.apache.org/thread/d9gm50kysgjcpbq448s2sy822kho6z6k > > Although it is an unexpected setting caused, we never kn

[DISCUSS] BookKeeper 4.15.2 release

2022-09-18 Thread Yong Zhang
Hi everyone, I want to discuss starting 4.15.2 release to resolve the regression mentioned here: https://lists.apache.org/thread/d9gm50kysgjcpbq448s2sy822kho6z6k Although it is an unexpected setting caused, we never know how the users to configure it. And we have a PR for fixing it, let's start a