The release tag has not been pushed yet?
I haven't seen rel/2.4.11 on github repo.
Andrew Purtell 于2022年3月19日周六 09:45写道：
> With 3 binding +1s including my own, 2 nonbinding +1s, and no 0 or -1
> votes, this vote passes.
>
> Thanks to all who voted on the release candidate!
>
>
> On Tue, Mar
So for #1, would you like to take a look at
https://github.com/apache/hbase/pull/4214
:)
Josh Elser 于2022年3月21日周一 04:50写道：
> Going through my inbox...
>
> 1. Great to have tooling which can validate (and fix) code which is not
> currently to style.
> 2. I would prefer a style guide (such as
In your earlier response you said:
> I'm also +1 for the last date 2022/07/21(seems adequate)
If this is ok, then we should do one more release and it would make sense to do
the one final release at the time of EOM. For your consideration.
> On Mar 20, 2022, at 8:43 PM, Reid Chan wrote:
>
> I did not claim that you ‘ran away’
I misread, pardon me :{
> Just that you did not do additional releases after 1.7.1.
Yep, I knew...
Let me schedule some time to do the 1.7.2 release
On Mon, Mar 21, 2022 at 11:20 AM Andrew Purtell
wrote:
> Greetings Reid. I did not claim that you ‘ran
[
https://issues.apache.org/jira/browse/HBASE-26870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-26870.
---
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to branch-2.5+.
Thanks [~busbey] for
Greetings Reid. I did not claim that you ‘ran away’ just to be clear. :-)
Pardon the informal language. Just that you did not do additional releases
after 1.7.1.
> On Mar 20, 2022, at 8:10 PM, Reid Chan wrote:
>
> Hi ah, I'm always here, still checking emails everyday, not running away.
>
Hi ah, I'm always here, still checking emails everyday, not running away.
Less active is just because I'm busy at work and training new colleagues,
some of them have been active in the HBase community for some time, and one
of them also became a committer. (kind of being active in another way
Xiaolin Ha created HBASE-26872:
--
Summary: Load rate calculator for cost functions should be more
precise
Key: HBASE-26872
URL: https://issues.apache.org/jira/browse/HBASE-26872
Project: HBase
Going through my inbox...
1. Great to have tooling which can validate (and fix) code which is not
currently to style.
2. I would prefer a style guide (such as Google's Java Style) which is
"generally accepted" by the Java industry at large and we can use as-is.
However, I don't feel strongly
Per the earlier discussion, to be comprehensive, there is also this rule:
4. If a change is in branch-2.4, branch-2.5, and branch-2: fix version = 2.4.x,
the version the change was released in. (Fix versions 2.5.0 and 2.6.0 will be
dropped for already released changes.)
The 2.5.0 change log
I have been setting both but don’t claim that is correct.
This is partly my fault for pushing back 2.5.0 for about six months since
cutting the branch. Partly this was waiting for always the next thing to
squeeze in, and partly life and work obligations getting in the way.
I am actually
Duo Zhang created HBASE-26871:
-
Summary: Client integration test fails on branch-2.x with
ClassNotFoundException
Key: HBASE-26871
URL: https://issues.apache.org/jira/browse/HBASE-26871
Project: HBase
Recently I've seen we set both 2.5.0 and 2.6.0 as fix versions for some
issues.
But from my understanding, I always choose to only set 2.5.0 as fix
versions if the patch has been committed to both branch-2 and branch-2.5.
The assumption is that all issues resolved in 2.5.0 should also be included
Duo Zhang created HBASE-26870:
-
Summary: Log4j2 integration is incorrect in nighly's client
integration test
Key: HBASE-26870
URL: https://issues.apache.org/jira/browse/HBASE-26870
Project: HBase
chenglei created HBASE-26869:
Summary: RSRpcServices.scan should deep clone cells when
RpcCallContext is null.
Key: HBASE-26869
URL: https://issues.apache.org/jira/browse/HBASE-26869
Project: HBase
Xiaolin Ha created HBASE-26868:
--
Summary: Introduce read/write request size metrics
Key: HBASE-26868
URL: https://issues.apache.org/jira/browse/HBASE-26868
Project: HBase
Issue Type: Sub-task
16 matches
Mail list logo
