[jira] [Comment Edited] (HBASE-29302) [hbase-thirdparty] Release hbase-thirdparty 4.1.11
[ https://issues.apache.org/jira/browse/HBASE-29302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955407#comment-17955407 ] Nihal Jain edited comment on HBASE-29302 at 5/31/25 12:45 PM: -- Release is complete: 4.1.11RC1 has been released as final release. Thank you [~revathy023] for your contribution of netty fix in this release and thank you reviewers. Thank you [~stoty], [~zhangduo], [~taklwu] for trying out the RC and voting. Thank you all who participated in the DISCUSS thread for the branching strategy for this release. Thanks [~cml] and Infra team for unblocking the build/git issues. Thank you [~ndimiduk] for your time helping me with my doubts around releasing. Checkout announce mail at https://lists.apache.org/thread/zkcpkkhgcbv9h06q6lgj8lvljkv7vsw4 for all details. was (Author: nihaljain.cs): Release is complete: 4.1.11RC1 has been released as final release. Thank you [~revathy023] for your contribution of netty fix in this release and thank you too reviewers. Thank you [~stoty], [~zhangduo], [~taklwu] for trying out the RC and voting. Thank you all who participated in the DISCUSS thread for the branching strategy for this release. Thanks [~cml] and Infra team for unblocking the build/git issues. Checkout announce mail at https://lists.apache.org/thread/zkcpkkhgcbv9h06q6lgj8lvljkv7vsw4 for all details. > [hbase-thirdparty] Release hbase-thirdparty 4.1.11 > -- > > Key: HBASE-29302 > URL: https://issues.apache.org/jira/browse/HBASE-29302 > Project: HBase > Issue Type: Umbrella > Components: community, thirdparty >Reporter: Nihal Jain >Assignee: Nihal Jain >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HBASE-29302) [hbase-thirdparty] Release hbase-thirdparty 4.1.11
[ https://issues.apache.org/jira/browse/HBASE-29302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17955407#comment-17955407 ] Nihal Jain edited comment on HBASE-29302 at 5/31/25 12:37 PM: -- Release is complete: 4.1.11RC1 has been released as final release. Thank you [~revathy023] for your contribution of netty fix in this release and thank you too reviewers. Thank you [~stoty], [~zhangduo], [~taklwu] for trying out the RC and voting. Thank you all who participated in the DISCUSS thread for the branching strategy for this release. Thanks [~cml] and Infra team for unblocking the build/git issues. Checkout announce mail at https://lists.apache.org/thread/zkcpkkhgcbv9h06q6lgj8lvljkv7vsw4 for all details. was (Author: nihaljain.cs): Release is complete, checkout announce mail at https://lists.apache.org/thread/zkcpkkhgcbv9h06q6lgj8lvljkv7vsw4 > [hbase-thirdparty] Release hbase-thirdparty 4.1.11 > -- > > Key: HBASE-29302 > URL: https://issues.apache.org/jira/browse/HBASE-29302 > Project: HBase > Issue Type: Umbrella > Components: community, thirdparty >Reporter: Nihal Jain >Assignee: Nihal Jain >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HBASE-29302) [hbase-thirdparty] Release hbase-thirdparty 4.1.11
[
https://issues.apache.org/jira/browse/HBASE-29302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953232#comment-17953232
]
Nihal Jain edited comment on HBASE-29302 at 5/21/25 6:59 PM:
-
Thank you [~ndimiduk] and [~zhangduo] for the reference, I have been able to
publish the keys at [https://dist.apache.org/repos/dist/release/hbase/KEYS]
{quote}Do we still need to use older jetty for branch-3+? If not, I prefer we
make a new branch for branch-2.x, and bump the version in master branch to 5.x.
{quote}
No we will completely drop usage of older jetty9 from master and be only on
jetty12, you can refer PR with the proposed change
[https://github.com/apache/hbase/pull/6783]
So as I understand we are looking to create 2 branches for hbase-thirdparty:
* Master which will be 5.x and be used by hbase-3+
** will contain jetty12 changes
** also we plan to make hbase-unsafe support jdk17 here, eventually?
** so basically eventually we will move to JDK 17 for this branch
* Fork current master as 4.x and this will be used by hbase-2.x
** will continue to be on jetty9
** this will still be using JDK8
I see we would double up maintenance with this as now we have to drive 2
releases for hbase-thirdparty and also each PR needs to be backported
appropriately.
Apart from JDK17, I am not sure how this will be useful as we can still have
multiple modules some being used by hbase-2.x while others used by 3.x+
Is my understanding correct? Should we start a discuss thread for this?
CC: [~stoty]
was (Author: nihaljain.cs):
Thank you [~ndimiduk] and [~zhangduo] for the reference, I have been able to
publish the keys at [https://dist.apache.org/repos/dist/release/hbase/KEYS]
{quote}Do we still need to use older jetty for branch-3+? If not, I prefer we
make a new branch for branch-2.x, and bump the version in master branch to 5.x.
{quote}
No we will completely drop usage of older jetty9 from master and be only on
jetty12, you can refer PR with the proposed change
[https://github.com/apache/hbase/pull/6783]
So as I understand we are looking to create 2 branches for hbase-thirdparty:
* Master which will be 5.x and be used by hbase-3+
** will contain jetty12 changes
** also we plan to make hbase-unsafe support jdk17 here, eventually?
** so basically eventually we will move to JDK 17 for this branch
* Fork current master as 4.x and this will be used by hbase-2.x
** will continue to be on jetty9
** this will still be using JDK8
I see we would double up maintenance with this as now we have to drive 2
releases for hbase-thirdparty and also each PR needs to be backported
appropriately.
Apart from JDK17, I am not sure how this will be useful as we can still have
multiple modules some being used by hbase-2.x while others used by 3.x+
Is my understanding correct? Should we start a discuss thread for this?
CC: [~stoty]
> [hbase-thirdparty] Release hbase-thirdparty 4.1.11
> --
>
> Key: HBASE-29302
> URL: https://issues.apache.org/jira/browse/HBASE-29302
> Project: HBase
> Issue Type: Umbrella
> Components: community, thirdparty
>Reporter: Nihal Jain
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (HBASE-29302) [hbase-thirdparty] Release hbase-thirdparty 4.1.11
[
https://issues.apache.org/jira/browse/HBASE-29302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953232#comment-17953232
]
Nihal Jain edited comment on HBASE-29302 at 5/21/25 7:00 PM:
-
Thank you [~ndimiduk] and [~zhangduo] for the reference, I have been able to
publish the keys at [https://dist.apache.org/repos/dist/release/hbase/KEYS]
{quote}Do we still need to use older jetty for branch-3+? If not, I prefer we
make a new branch for branch-2.x, and bump the version in master branch to 5.x.
{quote}
No we will completely drop usage of older jetty9 from master and be only on
jetty12, you can refer PR with the proposed change
[https://github.com/apache/hbase/pull/6783]. Please also refer
https://issues.apache.org/jira/browse/HBASE-29224 for high level plan!
So as I understand we are looking to create 2 branches for hbase-thirdparty:
* Master which will be 5.x and be used by hbase-3+
** will contain jetty12 changes
** also we plan to make hbase-unsafe support jdk17 here, eventually?
** so basically eventually we will move to JDK 17 for this branch
* Fork current master as 4.x and this will be used by hbase-2.x
** will continue to be on jetty9
** this will still be using JDK8
I see we would double up maintenance with this as now we have to drive 2
releases for hbase-thirdparty and also each PR needs to be backported
appropriately.
Apart from JDK17, I am not sure how this will be useful as we can still have
multiple modules some being used by hbase-2.x while others used by 3.x+
Is my understanding correct? Should we start a discuss thread for this?
CC: [~stoty]
was (Author: nihaljain.cs):
Thank you [~ndimiduk] and [~zhangduo] for the reference, I have been able to
publish the keys at [https://dist.apache.org/repos/dist/release/hbase/KEYS]
{quote}Do we still need to use older jetty for branch-3+? If not, I prefer we
make a new branch for branch-2.x, and bump the version in master branch to 5.x.
{quote}
No we will completely drop usage of older jetty9 from master and be only on
jetty12, you can refer PR with the proposed change
[https://github.com/apache/hbase/pull/6783]
So as I understand we are looking to create 2 branches for hbase-thirdparty:
* Master which will be 5.x and be used by hbase-3+
** will contain jetty12 changes
** also we plan to make hbase-unsafe support jdk17 here, eventually?
** so basically eventually we will move to JDK 17 for this branch
* Fork current master as 4.x and this will be used by hbase-2.x
** will continue to be on jetty9
** this will still be using JDK8
I see we would double up maintenance with this as now we have to drive 2
releases for hbase-thirdparty and also each PR needs to be backported
appropriately.
Apart from JDK17, I am not sure how this will be useful as we can still have
multiple modules some being used by hbase-2.x while others used by 3.x+
Is my understanding correct? Should we start a discuss thread for this?
CC: [~stoty]
> [hbase-thirdparty] Release hbase-thirdparty 4.1.11
> --
>
> Key: HBASE-29302
> URL: https://issues.apache.org/jira/browse/HBASE-29302
> Project: HBase
> Issue Type: Umbrella
> Components: community, thirdparty
>Reporter: Nihal Jain
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (HBASE-29302) [hbase-thirdparty] Release hbase-thirdparty 4.1.11
[ https://issues.apache.org/jira/browse/HBASE-29302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953235#comment-17953235 ] Istvan Toth edited comment on HBASE-29302 at 5/21/25 7:11 PM: -- While there is nothing technically wrong with having two thirdparty branches, maintaining (and releasing) them would require us to make twice as many releases. >From a release workload perspective having a single branch with duplicate >modules sounds like less work to me, [~zhangduo]. (Same argument as Nihal's) was (Author: stoty): While there is nothing technically wrong with having two thirdparty branches, maintaining (and releasing) them would require us to make twice as many releases. >From a release workload perspective having a single branch with duplicate >modules sounds like less work to me, [~zhangduo]. > [hbase-thirdparty] Release hbase-thirdparty 4.1.11 > -- > > Key: HBASE-29302 > URL: https://issues.apache.org/jira/browse/HBASE-29302 > Project: HBase > Issue Type: Umbrella > Components: community, thirdparty >Reporter: Nihal Jain >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HBASE-29302) [hbase-thirdparty] Release hbase-thirdparty 4.1.11
[
https://issues.apache.org/jira/browse/HBASE-29302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953232#comment-17953232
]
Nihal Jain edited comment on HBASE-29302 at 5/21/25 6:59 PM:
-
Thank you [~ndimiduk] and [~zhangduo] for the reference, I have been able to
publish the keys at [https://dist.apache.org/repos/dist/release/hbase/KEYS]
{quote}Do we still need to use older jetty for branch-3+? If not, I prefer we
make a new branch for branch-2.x, and bump the version in master branch to 5.x.
{quote}
No we will completely drop usage of older jetty9 from master and be only on
jetty12, you can refer PR with the proposed change
[https://github.com/apache/hbase/pull/6783]
So as I understand we are looking to create 2 branches for hbase-thirdparty:
* Master which will be 5.x and be used by hbase-3+
** will contain jetty12 changes
** also we plan to make hbase-unsafe support jdk17 here, eventually?
** so basically eventually we will move to JDK 17 for this branch
* Fork current master as 4.x and this will be used by hbase-2.x
** will continue to be on jetty9
** this will still be using JDK8
I see we would double up maintenance with this as now we have to drive 2
releases for hbase-thirdparty and also each PR needs to be backported
appropriately.
Apart from JDK17, I am not sure how this will be useful as we can still have
multiple modules some being used by hbase-2.x while others used by 3.x+
Is my understanding correct? Should we start a discuss thread for this?
CC: [~stoty]
was (Author: nihaljain.cs):
Thank you [~ndimiduk] and [~zhangduo] for the reference, I have been able to
publish the keys at [https://dist.apache.org/repos/dist/release/hbase/KEYS]
{quote}Do we still need to use older jetty for branch-3+? If not, I prefer we
make a new branch for branch-2.x, and bump the version in master branch to 5.x.
{quote}
No we will completely drop usage of older jetty9 from master and be only on
jetty12, you can refer PR with the proposed change
[https://github.com/apache/hbase/pull/6783]
So as I understand we are looking to create 2 branches for hbase-thirdparty:
* Master which will be 5.x and be used by hbase-3+
*
** will contain jetty12 changes
** also we plan to make hbase-unsafe support jdk17 here, eventually?
** so basically eventually we will move to JDK 17 for this branch
* Fork current master as 4.x and this will be used by hbase-2.x
** will continue to be on jetty9
** this will still be using JDK8
I see we would double up maintenance with this as now we have to drive 2
releases for hbase-thirdparty and also each PR needs to be backported
appropriately.
Apart from JDK17, I am not sure how this will be useful as we can still have
multiple modules some being used by hbase-2.x while others used by 3.x+
Is my understanding correct? Should we start a discuss thread for this?
CC: [~stoty]
> [hbase-thirdparty] Release hbase-thirdparty 4.1.11
> --
>
> Key: HBASE-29302
> URL: https://issues.apache.org/jira/browse/HBASE-29302
> Project: HBase
> Issue Type: Umbrella
> Components: community, thirdparty
>Reporter: Nihal Jain
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (HBASE-29302) [hbase-thirdparty] Release hbase-thirdparty 4.1.11
[
https://issues.apache.org/jira/browse/HBASE-29302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953232#comment-17953232
]
Nihal Jain edited comment on HBASE-29302 at 5/21/25 6:58 PM:
-
Thank you [~ndimiduk] and [~zhangduo] for the reference, I have been able to
publish the keys at [https://dist.apache.org/repos/dist/release/hbase/KEYS]
{quote}Do we still need to use older jetty for branch-3+? If not, I prefer we
make a new branch for branch-2.x, and bump the version in master branch to 5.x.
{quote}
No we will completely drop usage of older jetty9 from master and be only on
jetty12, you can refer PR with the proposed change
[https://github.com/apache/hbase/pull/6783]
So as I understand we are looking to create 2 branches for hbase-thirdparty:
* Master which will be 5.x and be used by hbase-3+
*
** will contain jetty12 changes
** also we plan to make hbase-unsafe support jdk17 here, eventually?
** so basically eventually we will move to JDK 17 for this branch
* Fork current master as 4.x and this will be used by hbase-2.x
** will continue to be on jetty9
** this will still be using JDK8
I see we would double up maintenance with this as now we have to drive 2
releases for hbase-thirdparty and also each PR needs to be backported
appropriately.
Apart from JDK17, I am not sure how this will be useful as we can still have
multiple modules some being used by hbase-2.x while others used by 3.x+
Is my understanding correct? Should we start a discuss thread for this?
CC: [~stoty]
was (Author: nihaljain.cs):
Thank you [~ndimiduk] and [~zhangduo] for the reference, I have been able to
publish the keys at [https://dist.apache.org/repos/dist/release/hbase/KEYS]
> Do we still need to use older jetty for branch-3+? If not, I prefer we make a
> new branch for branch-2.x, and bump the version in master branch to 5.x.
No we will completely drop usage of older jetty9 from master and be only on
jetty12, you can refer PR with the proposed change
[https://github.com/apache/hbase/pull/6783]
So as I understand we are looking to create 2 branches for hbase-thirdparty:
* Master which will be 5.x and be used by hbase-3+
** will contain jetty12 changes
** also we plan to make hbase-unsafe support jdk17 here, eventually?
** so basically eventually we will move to JDK 17 for this branch
* Fork current master as 4.x and this will be used by hbase-2.x
** will continue to be on jetty9
** this will still be using JDK8
I see we would double up maintenance with this as now we have to drive 2
releases for hbase-thirdparty and also each PR needs to be backported
appropriately.
Apart from JDK17, I am not sure how this will be useful as we can still have
multiple modules some being used by hbase-2.x while others used by 3.x+
Is my understanding correct? Should we start a discuss thread for this?
CC: [~stoty]
> [hbase-thirdparty] Release hbase-thirdparty 4.1.11
> --
>
> Key: HBASE-29302
> URL: https://issues.apache.org/jira/browse/HBASE-29302
> Project: HBase
> Issue Type: Umbrella
> Components: community, thirdparty
>Reporter: Nihal Jain
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (HBASE-29302) [hbase-thirdparty] Release hbase-thirdparty 4.1.11
[ https://issues.apache.org/jira/browse/HBASE-29302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951331#comment-17951331 ] Nihal Jain edited comment on HBASE-29302 at 5/14/25 6:22 AM: - > Is jetty 12 compatible with branch-2.x? We plan to set to jetty12 for branch-3+. In order to consume jetty 12 for branch 2 we have to make minimum java as 17 so it is not possible right away. So we are now bundling a new module for jetty12 which branch-3+ will use and branch-2 will keep using jetty 9 as before. Please see https://issues.apache.org/jira/browse/HBASE-29224 and [https://github.com/apache/hbase-thirdparty/pull/131] > Do we need to bump to 5.x for thirdparty? We can bump to 5.x if we decide to drop jetty 9 in future or we could do right away. But I do not see any breaking change that this version introduces. It's just that we have introduced 2 new modules for branch-3+ was (Author: nihaljain.cs): > Is jetty 12 compatible with branch-2.x? We plan to backport this to branch-3+. In order to consume jetty 12 for branch 2 we have to mak min java as 17 so it is not possible right away. So we are now bundling a new module for jetty12 which branch-3+ will use and branch-2 will keep using jetty 9 as before. Please see https://issues.apache.org/jira/browse/HBASE-29224 and [https://github.com/apache/hbase-thirdparty/pull/131] > Do we need to bump to 5.x for thirdparty? We can bump to 5.x if we decide to drop jetty 9 in future or we could do right away. But I do not see any breaking change that this version introduces. It's just that we have introduced 2 new modules for branch-3+ > [hbase-thirdparty] Release hbase-thirdparty 4.1.11 > -- > > Key: HBASE-29302 > URL: https://issues.apache.org/jira/browse/HBASE-29302 > Project: HBase > Issue Type: Umbrella > Components: community, thirdparty >Reporter: Nihal Jain >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HBASE-29302) [hbase-thirdparty] Release hbase-thirdparty 4.1.11
[ https://issues.apache.org/jira/browse/HBASE-29302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950514#comment-17950514 ] Nihal Jain edited comment on HBASE-29302 at 5/9/25 1:32 PM: I want to volunteer for release of next hbase-thirdparty, we have a bunch of CVEs to consume in hbase: netty, gson etc. Also I need to consume jetty 12 change done as part of HBASE-29225 Please let me know if I can take up the release task. I target to complete this by next weekend, given no hiccups (as it would be first time I will try the release process :)) CC: [~zhangduo] [~stoty] [~ndimiduk] [~apurtell] was (Author: nihaljain.cs): I want to volunteer for release of next hbase-thirdparty, we have a bunch of CVEs to consume in hbase: netty, gson etc. Also I need to consume jetty 12 change done as part of HBASE-29225 Please let me know if I can take up the release task. I target to complete this by next weekend, given no hiccups (as it would be first time I will try the release process :)) CC: [~zhangduo] [~stoty] [~ndimiduk] [~apurtell] h1. > [hbase-thirdparty] Release hbase-thirdparty 4.1.11 > -- > > Key: HBASE-29302 > URL: https://issues.apache.org/jira/browse/HBASE-29302 > Project: HBase > Issue Type: Umbrella > Components: community, thirdparty >Reporter: Nihal Jain >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HBASE-29302) [hbase-thirdparty] Release hbase-thirdparty 4.1.11
[ https://issues.apache.org/jira/browse/HBASE-29302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950514#comment-17950514 ] Nihal Jain edited comment on HBASE-29302 at 5/9/25 1:35 PM: I want to volunteer for release of next hbase-thirdparty, we have a bunch of CVEs to consume in hbase: netty, gson etc. Also I need to consume jetty 12 change done as part of HBASE-29225 i.e. "Add module for Jetty 12 with EE8 to hbase-thirdparty" Please let me know if I can take up the release task. I target to complete this by next weekend, given no hiccups (as it would be first time I will try the release process :)) CC: [~zhangduo] [~stoty] [~ndimiduk] [~apurtell] was (Author: nihaljain.cs): I want to volunteer for release of next hbase-thirdparty, we have a bunch of CVEs to consume in hbase: netty, gson etc. Also I need to consume jetty 12 change done as part of HBASE-29225 Please let me know if I can take up the release task. I target to complete this by next weekend, given no hiccups (as it would be first time I will try the release process :)) CC: [~zhangduo] [~stoty] [~ndimiduk] [~apurtell] > [hbase-thirdparty] Release hbase-thirdparty 4.1.11 > -- > > Key: HBASE-29302 > URL: https://issues.apache.org/jira/browse/HBASE-29302 > Project: HBase > Issue Type: Umbrella > Components: community, thirdparty >Reporter: Nihal Jain >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (HBASE-29302) [hbase-thirdparty] Release hbase-thirdparty 4.1.11
[ https://issues.apache.org/jira/browse/HBASE-29302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950514#comment-17950514 ] Nihal Jain edited comment on HBASE-29302 at 5/9/25 1:31 PM: I want to volunteer for release of next hbase-thirdparty, we have a bunch of CVEs to consume in hbase: netty, gson etc. Also I need to consume jetty 12 change done as part of HBASE-29225 Please let me know if I can take up the release task. I target to complete this by next weekend, given no hiccups (as it would be first time I will try the release process :)) CC: [~zhangduo] [~stoty] [~ndimiduk] [~apurtell] h1. was (Author: nihaljain.cs): I want to volunteer for release of next hbase-thirdparty, we have a bunch of CVEs to consume in hbase: netty, gson etc. Also I need to consume jetty 12 change done as part of HBASE-29225 Please let me know if I can take up the release task. I target to complete this by next weekend. CC: [~zhangduo] [~stoty] [~ndimiduk] [~apurtell] h1. > [hbase-thirdparty] Release hbase-thirdparty 4.1.11 > -- > > Key: HBASE-29302 > URL: https://issues.apache.org/jira/browse/HBASE-29302 > Project: HBase > Issue Type: Umbrella > Components: community, thirdparty >Reporter: Nihal Jain >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
