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 <ap...@apache.org> on 2022/04/02 19:15:05 UTC
Please pause any additional significant changes to branch-2.5
At this point I would like to declare branch-2.5 closed for any additional
significant changes. It should be in good shape to post 2.5.0RC0 within the
month.
We have landed an update of logging to log4j2. A remaining minor issue I am
aware of is HBASE-26854, which I will fix this week. If you know of any
other related issue please do let me know.
Per our recent discussion on dev@ on coordinating the release of
StoreFileTracker protobuf definitions and hbase-operator-tools support for
SFT structures, SFT was backported to branch-2.5 via HBASE-26826. The 2.5.0
release will ship with enabling bits in hbase-protocol-shaded. We should
arrange a concurrent release of hbase-operator-tools support for SFT
structures if possible, but that does not block the 2.5.0 release in my
opinion because SFT will be called out as 'experimental' in the release
announcement.
Nick mentioned on HBASE-26419 that he thinks the otel tracing work is now
in good enough shape for a release of 2.5.0. Let's pause additional changes
to the branch in that regard except for bug fixes until after 2.5.0 is
released.
I have a promised documentation update (HBASE-26330) and a minor
operability improvement (HBASE-26192) that I have been putting off that
should be finished now that a RC is imminent. I will wrap them up shortly.
If you have any other minor work that should go in to 2.5.0 and haven't
gotten to it yet, now is the time, in the next week or so, to commit it.
--
Best regards,
Andrew
Re: Please pause any additional significant changes to branch-2.5
Posted by Andrew Purtell <ap...@apache.org>.
Clarification: Please continue to commit bug fixes to branch-2.5. A bug fix
is not a "significant change". They fix a feature or behavior already in
place.
On Sat, May 7, 2022 at 11:35 AM Andrew Purtell <ap...@apache.org> wrote:
> The spotless application to branch-2.5 was recently completed. We are down
> to five in progress tasks.
>
> HBASE-25915: 'mobdir' overlaps in HFileLink.mobPath (Patch Available)
> HBASE-26192: hbck.jsp should provide an JSON formatted output option
> (Open, but Minor)
> HBASE-26342: Support custom paths of independent configuration and pool
> for hfile cleaner (Patch Available)
> HBASE-26854: Shell startup logs a bunch of noise (Open, but Trivial)
> HBASE-26912: [dependabot] Bump checkstyle from 8.28 to 8.29 (Open, but
> Trivial)
>
> Two are in patch available status and I will shepherd them in along with
> finishing the other three tasks that are all on my plate in the coming few
> days. After a pass over tests to clean up flakes and issues, if necessary,
> 2.5.0RC0 is imminent.
>
--
Best regards,
Andrew
Unrest, ignorance distilled, nihilistic imbeciles -
It's what we’ve earned
Welcome, apocalypse, what’s taken you so long?
Bring us the fitting end that we’ve been counting on
- A23, Welcome, Apocalypse
Re: Please pause any additional significant changes to branch-2.5
Posted by Andrew Purtell <ap...@apache.org>.
The spotless application to branch-2.5 was recently completed. We are down
to five in progress tasks.
HBASE-25915: 'mobdir' overlaps in HFileLink.mobPath (Patch Available)
HBASE-26192: hbck.jsp should provide an JSON formatted output option (Open,
but Minor)
HBASE-26342: Support custom paths of independent configuration and pool for
hfile cleaner (Patch Available)
HBASE-26854: Shell startup logs a bunch of noise (Open, but Trivial)
HBASE-26912: [dependabot] Bump checkstyle from 8.28 to 8.29 (Open, but
Trivial)
Two are in patch available status and I will shepherd them in along with
finishing the other three tasks that are all on my plate in the coming few
days. After a pass over tests to clean up flakes and issues, if necessary,
2.5.0RC0 is imminent.
Re: Please pause any additional significant changes to branch-2.5
Posted by Andrew Purtell <ap...@apache.org>.
I should also mention that we will most likely be running 'spotless:apply'
against branch-2.5 sources and committing the resulting changes prior to
release of 2.5.0, in order to minimize future divergence between branch-2.5
and branch-2 or master branches. Although these changes will touch most
source files they will not modify the code semantically, so although it is
'significant' because of its scope, it is not significant in the way that I
mean for this thread, which can be defined as having stability or
compatibility risks.
On Sat, Apr 2, 2022 at 12:15 PM Andrew Purtell <ap...@apache.org> wrote:
> At this point I would like to declare branch-2.5 closed for any additional
> significant changes. It should be in good shape to post 2.5.0RC0 within the
> month.
>
> We have landed an update of logging to log4j2. A remaining minor issue I
> am aware of is HBASE-26854, which I will fix this week. If you know of any
> other related issue please do let me know.
>
> Per our recent discussion on dev@ on coordinating the release of
> StoreFileTracker protobuf definitions and hbase-operator-tools support for
> SFT structures, SFT was backported to branch-2.5 via HBASE-26826. The 2.5.0
> release will ship with enabling bits in hbase-protocol-shaded. We should
> arrange a concurrent release of hbase-operator-tools support for SFT
> structures if possible, but that does not block the 2.5.0 release in my
> opinion because SFT will be called out as 'experimental' in the release
> announcement.
>
> Nick mentioned on HBASE-26419 that he thinks the otel tracing work is now
> in good enough shape for a release of 2.5.0. Let's pause additional changes
> to the branch in that regard except for bug fixes until after 2.5.0 is
> released.
>
> I have a promised documentation update (HBASE-26330) and a minor
> operability improvement (HBASE-26192) that I have been putting off that
> should be finished now that a RC is imminent. I will wrap them up shortly.
> If you have any other minor work that should go in to 2.5.0 and haven't
> gotten to it yet, now is the time, in the next week or so, to commit it.
>
> --
> Best regards,
> Andrew
>
--
Best regards,
Andrew
Unrest, ignorance distilled, nihilistic imbeciles -
It's what we’ve earned
Welcome, apocalypse, what’s taken you so long?
Bring us the fitting end that we’ve been counting on
- A23, Welcome, Apocalypse