You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Andrew Purtell <an...@gmail.com> on 2021/01/04 02:15:39 UTC
[NOTICE] Upcoming patch releases for 2.x code lines
Some new authorization checks were just added to RsRpcServices. Unless someone else wants to RM for 2.2 and 2.3, I will propose new patch level RCs for 2.2, 2.3, and 2.4 for voting next week.
The prep work will happen this week. I plan to start at the release tag for the last release in each 2.x, cherry pick the relevant commits, and do some preflight checks.
If you have any concerns or know of other critical issues that could warrant inclusion, please respond.
Re: [NOTICE] Upcoming patch releases for 2.x code lines
Posted by Andrew Purtell <ap...@apache.org>.
Thanks Viraj.
Over the weekend I ran unit test suites in a loop and except for the known
issue with JDK8 and hbase-asyncfs things look pretty good.
On Thu, Jan 7, 2021 at 6:06 AM Viraj Jasani <vj...@apache.org> wrote:
> Some relevant Jiras were pending with branch-2.2 backports.
> Just finished it. All relevant commits are now present on all
> active branches (including branch-1).
>
> On 2021/01/05 18:55:05, Nick Dimiduk <nd...@apache.org> wrote:
> > Hi Andrew,
> >
> > We're anyways due for 2.3.4. The plan is to have a candidate up this
> week.
> > Assuming the patches you're targeting are on branch-2.3, I think you can
> > omit 2.3 from your process.
> >
> > Thanks,
> > Nick
> >
> > On Sun, Jan 3, 2021 at 6:15 PM Andrew Purtell <an...@gmail.com>
> > wrote:
> >
> > > Some new authorization checks were just added to RsRpcServices. Unless
> > > someone else wants to RM for 2.2 and 2.3, I will propose new patch
> level
> > > RCs for 2.2, 2.3, and 2.4 for voting next week.
> > >
> > > The prep work will happen this week. I plan to start at the release tag
> > > for the last release in each 2.x, cherry pick the relevant commits,
> and do
> > > some preflight checks.
> > >
> > > If you have any concerns or know of other critical issues that could
> > > warrant inclusion, please respond.
> > >
> > >
> >
>
--
Best regards,
Andrew
Words like orphans lost among the crosstalk, meaning torn from truth's
decrepit hands
- A23, Crosstalk
Re: [NOTICE] Upcoming patch releases for 2.x code lines
Posted by Viraj Jasani <vj...@apache.org>.
Some relevant Jiras were pending with branch-2.2 backports.
Just finished it. All relevant commits are now present on all
active branches (including branch-1).
On 2021/01/05 18:55:05, Nick Dimiduk <nd...@apache.org> wrote:
> Hi Andrew,
>
> We're anyways due for 2.3.4. The plan is to have a candidate up this week.
> Assuming the patches you're targeting are on branch-2.3, I think you can
> omit 2.3 from your process.
>
> Thanks,
> Nick
>
> On Sun, Jan 3, 2021 at 6:15 PM Andrew Purtell <an...@gmail.com>
> wrote:
>
> > Some new authorization checks were just added to RsRpcServices. Unless
> > someone else wants to RM for 2.2 and 2.3, I will propose new patch level
> > RCs for 2.2, 2.3, and 2.4 for voting next week.
> >
> > The prep work will happen this week. I plan to start at the release tag
> > for the last release in each 2.x, cherry pick the relevant commits, and do
> > some preflight checks.
> >
> > If you have any concerns or know of other critical issues that could
> > warrant inclusion, please respond.
> >
> >
>
Re: [NOTICE] Upcoming patch releases for 2.x code lines
Posted by Nick Dimiduk <nd...@apache.org>.
Hi Andrew,
We're anyways due for 2.3.4. The plan is to have a candidate up this week.
Assuming the patches you're targeting are on branch-2.3, I think you can
omit 2.3 from your process.
Thanks,
Nick
On Sun, Jan 3, 2021 at 6:15 PM Andrew Purtell <an...@gmail.com>
wrote:
> Some new authorization checks were just added to RsRpcServices. Unless
> someone else wants to RM for 2.2 and 2.3, I will propose new patch level
> RCs for 2.2, 2.3, and 2.4 for voting next week.
>
> The prep work will happen this week. I plan to start at the release tag
> for the last release in each 2.x, cherry pick the relevant commits, and do
> some preflight checks.
>
> If you have any concerns or know of other critical issues that could
> warrant inclusion, please respond.
>
>