You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by Istvan Toth <st...@apache.org> on 2021/10/22 07:00:08 UTC
[DISCUSS] Releasing 5.1.3 / 4.16.2
Hi!
The last 5.1 and 4.16 releases were respectively made in June and May.
We've accumulated a number of good fixes in the meantime, I think now may
be a good time to do
patch releases, before the holiday season comes, which would make it more
difficult to do it.
I also get the impression that quite a few low-risk fixes have not been
backported to the maintenance branches, we should do a pass on backporting
those patches as well.
Do you think that this is a good time for this, or should we wait until
next year ?
Do we have some specific fix that we want to make sure gets into the next
maintenance release ?
If we agree to do this does anyone volunteer to be the RM for either?
regards
Istvan
Re: [DISCUSS] Releasing 5.1.3 / 4.16.2
Posted by Istvan Toth <st...@apache.org>.
4.16 is in even worse shape:
PHOENIX-6511 +addendums
PHOENIX-6338
PHOENIX-6346
PHOENIX-6347
PHOENIX-6351
PHOENIX-6356
PHOENIX-6420
PHOENIX-6421
PHOENIX-6423
PHOENIX-6424
PHOENIX-6436
PHOENIX-6444
PHOENIX-6451
PHOENIX-6456
PHOENIX-6462
PHOENIX-6472
PHOENIX-6476
PHOENIX-6498
PHOENIX-6507
PHOENIX-6511
PHOENIX-6528
PHOENIX-6543
I'm not committing to fixing this now, please reply here if you start
working on this.
On Fri, Oct 29, 2021 at 5:10 PM Istvan Toth <st...@apache.org> wrote:
> I've compared master and 5.1, and found the following missing fixes from
> 5.1:
> PHOENIX-6462
> PHOENIX-6472
> PHOENIX-6498
> PHOENIX-6507
> PHOENIX-6528
> PHOENIX-6577 (this one was me)
>
> I'm running mvn verify on them, then I will commit them to 5.1.
>
> Istvan
>
> On Wed, Oct 27, 2021 at 7:47 AM Istvan Toth <st...@apache.org> wrote:
>
>> Thank you Viraj.
>>
>>
>> On Sat, Oct 23, 2021 at 8:22 AM Viraj Jasani <vj...@apache.org> wrote:
>>
>>> Thanks Luoc. 2.4.8 is also about to be released soon (most likely next
>>> week). We might also want to consider upgrading the dependency for 2.4
>>> release line after 2.4.8 is released.
>>>
>>> Thanks Istvan for starting this thread. +1 for new 5.1 patch release. If
>>> not done till 15th Nov, I can volunteer to be RM to complete it before
>>> start of Dec.
>>>
>>>
>>> On Fri, 22 Oct 2021 at 9:03 PM, luoc <lu...@qq.com.invalid> wrote:
>>>
>>> > Hello, Istvan. I am going to create a ticket to upgrade the hbase
>>> > dependency with the latest 2.3.7. And before that happens, I
>>> will
>>> > test them in our test cluster.
>>> >
>>> >
>>> > -- luoc
>>> >
>>> >
>>> >
>>> >
>>> > ------------------ 原始邮件 ------------------
>>> > 发件人:
>>> > "dev"
>>> > <
>>> > stoty@apache.org>;
>>> > 发送时间: 2021年10月22日(星期五) 下午3:00
>>> > 收件人: "dev"<dev@phoenix.apache.org>;
>>> >
>>> > 主题: [DISCUSS] Releasing 5.1.3 / 4.16.2
>>> >
>>> >
>>> >
>>> > Hi!
>>> >
>>> > The last 5.1 and 4.16 releases were respectively made in June and May.
>>> > We've accumulated a number of good fixes in the meantime, I think now
>>> may
>>> > be a good time to do
>>> > patch releases, before the holiday season comes, which would make it
>>> more
>>> > difficult to do it.
>>> >
>>> > I also get the impression that quite a few low-risk fixes have not been
>>> > backported to the maintenance branches, we should do a pass on
>>> backporting
>>> > those patches as well.
>>> >
>>> > Do you think that this is a good time for this, or should we wait until
>>> > next year ?
>>> > Do we have some specific fix that we want to make sure gets into the
>>> next
>>> > maintenance release ?
>>> > If we agree to do this does anyone volunteer to be the RM for either?
>>> >
>>> > regards
>>> > Istvan
>>>
>>
Re: [DISCUSS] Releasing 5.1.3 / 4.16.2
Posted by Istvan Toth <st...@apache.org>.
I've compared master and 5.1, and found the following missing fixes from
5.1:
PHOENIX-6462
PHOENIX-6472
PHOENIX-6498
PHOENIX-6507
PHOENIX-6528
PHOENIX-6577 (this one was me)
I'm running mvn verify on them, then I will commit them to 5.1.
Istvan
On Wed, Oct 27, 2021 at 7:47 AM Istvan Toth <st...@apache.org> wrote:
> Thank you Viraj.
>
>
> On Sat, Oct 23, 2021 at 8:22 AM Viraj Jasani <vj...@apache.org> wrote:
>
>> Thanks Luoc. 2.4.8 is also about to be released soon (most likely next
>> week). We might also want to consider upgrading the dependency for 2.4
>> release line after 2.4.8 is released.
>>
>> Thanks Istvan for starting this thread. +1 for new 5.1 patch release. If
>> not done till 15th Nov, I can volunteer to be RM to complete it before
>> start of Dec.
>>
>>
>> On Fri, 22 Oct 2021 at 9:03 PM, luoc <lu...@qq.com.invalid> wrote:
>>
>> > Hello, Istvan. I am going to create a ticket to upgrade the hbase
>> > dependency with the latest 2.3.7. And before that happens, I
>> will
>> > test them in our test cluster.
>> >
>> >
>> > -- luoc
>> >
>> >
>> >
>> >
>> > ------------------ 原始邮件 ------------------
>> > 发件人:
>> > "dev"
>> > <
>> > stoty@apache.org>;
>> > 发送时间: 2021年10月22日(星期五) 下午3:00
>> > 收件人: "dev"<dev@phoenix.apache.org>;
>> >
>> > 主题: [DISCUSS] Releasing 5.1.3 / 4.16.2
>> >
>> >
>> >
>> > Hi!
>> >
>> > The last 5.1 and 4.16 releases were respectively made in June and May.
>> > We've accumulated a number of good fixes in the meantime, I think now
>> may
>> > be a good time to do
>> > patch releases, before the holiday season comes, which would make it
>> more
>> > difficult to do it.
>> >
>> > I also get the impression that quite a few low-risk fixes have not been
>> > backported to the maintenance branches, we should do a pass on
>> backporting
>> > those patches as well.
>> >
>> > Do you think that this is a good time for this, or should we wait until
>> > next year ?
>> > Do we have some specific fix that we want to make sure gets into the
>> next
>> > maintenance release ?
>> > If we agree to do this does anyone volunteer to be the RM for either?
>> >
>> > regards
>> > Istvan
>>
>
Re: [DISCUSS] Releasing 5.1.3 / 4.16.2
Posted by Istvan Toth <st...@apache.org>.
Thank you Viraj.
On Sat, Oct 23, 2021 at 8:22 AM Viraj Jasani <vj...@apache.org> wrote:
> Thanks Luoc. 2.4.8 is also about to be released soon (most likely next
> week). We might also want to consider upgrading the dependency for 2.4
> release line after 2.4.8 is released.
>
> Thanks Istvan for starting this thread. +1 for new 5.1 patch release. If
> not done till 15th Nov, I can volunteer to be RM to complete it before
> start of Dec.
>
>
> On Fri, 22 Oct 2021 at 9:03 PM, luoc <lu...@qq.com.invalid> wrote:
>
> > Hello, Istvan. I am going to create a ticket to upgrade the hbase
> > dependency with the latest 2.3.7. And before that happens, I
> will
> > test them in our test cluster.
> >
> >
> > -- luoc
> >
> >
> >
> >
> > ------------------ 原始邮件 ------------------
> > 发件人:
> > "dev"
> > <
> > stoty@apache.org>;
> > 发送时间: 2021年10月22日(星期五) 下午3:00
> > 收件人: "dev"<dev@phoenix.apache.org>;
> >
> > 主题: [DISCUSS] Releasing 5.1.3 / 4.16.2
> >
> >
> >
> > Hi!
> >
> > The last 5.1 and 4.16 releases were respectively made in June and May.
> > We've accumulated a number of good fixes in the meantime, I think now may
> > be a good time to do
> > patch releases, before the holiday season comes, which would make it more
> > difficult to do it.
> >
> > I also get the impression that quite a few low-risk fixes have not been
> > backported to the maintenance branches, we should do a pass on
> backporting
> > those patches as well.
> >
> > Do you think that this is a good time for this, or should we wait until
> > next year ?
> > Do we have some specific fix that we want to make sure gets into the next
> > maintenance release ?
> > If we agree to do this does anyone volunteer to be the RM for either?
> >
> > regards
> > Istvan
>
Re: [DISCUSS] Releasing 5.1.3 / 4.16.2
Posted by Viraj Jasani <vj...@apache.org>.
Thanks Luoc. 2.4.8 is also about to be released soon (most likely next
week). We might also want to consider upgrading the dependency for 2.4
release line after 2.4.8 is released.
Thanks Istvan for starting this thread. +1 for new 5.1 patch release. If
not done till 15th Nov, I can volunteer to be RM to complete it before
start of Dec.
On Fri, 22 Oct 2021 at 9:03 PM, luoc <lu...@qq.com.invalid> wrote:
> Hello, Istvan. I am going to create a ticket to upgrade the hbase
> dependency with the latest 2.3.7. And before that happens, I will
> test them in our test cluster.
>
>
> -- luoc
>
>
>
>
> ------------------ 原始邮件 ------------------
> 发件人:
> "dev"
> <
> stoty@apache.org>;
> 发送时间: 2021年10月22日(星期五) 下午3:00
> 收件人: "dev"<dev@phoenix.apache.org>;
>
> 主题: [DISCUSS] Releasing 5.1.3 / 4.16.2
>
>
>
> Hi!
>
> The last 5.1 and 4.16 releases were respectively made in June and May.
> We've accumulated a number of good fixes in the meantime, I think now may
> be a good time to do
> patch releases, before the holiday season comes, which would make it more
> difficult to do it.
>
> I also get the impression that quite a few low-risk fixes have not been
> backported to the maintenance branches, we should do a pass on backporting
> those patches as well.
>
> Do you think that this is a good time for this, or should we wait until
> next year ?
> Do we have some specific fix that we want to make sure gets into the next
> maintenance release ?
> If we agree to do this does anyone volunteer to be the RM for either?
>
> regards
> Istvan
回复：[DISCUSS] Releasing 5.1.3 / 4.16.2
Posted by luoc <lu...@qq.com.INVALID>.
Hello, Istvan. I am going to create a ticket to upgrade the hbase dependency with the latest 2.3.7. And before that happens, I will test them in our test cluster.
-- luoc
------------------ 原始邮件 ------------------
发件人: "dev" <stoty@apache.org>;
发送时间: 2021年10月22日(星期五) 下午3:00
收件人: "dev"<dev@phoenix.apache.org>;
主题: [DISCUSS] Releasing 5.1.3 / 4.16.2
Hi!
The last 5.1 and 4.16 releases were respectively made in June and May.
We've accumulated a number of good fixes in the meantime, I think now may
be a good time to do
patch releases, before the holiday season comes, which would make it more
difficult to do it.
I also get the impression that quite a few low-risk fixes have not been
backported to the maintenance branches, we should do a pass on backporting
those patches as well.
Do you think that this is a good time for this, or should we wait until
next year ?
Do we have some specific fix that we want to make sure gets into the next
maintenance release ?
If we agree to do this does anyone volunteer to be the RM for either?
regards
Istvan