the check that Stephen is referring to is for logic around lease recovery
and not stream flush/sync. the lease recovery is specific to DFS IIRC and
doesn't have a FileSystem marker.
On Wed, Mar 15, 2023 at 3:22 PM Andrew Purtell wrote:
> So we can test StreamCapabilities in code, in worst case
Sean Busbey created HBASE-27425:
---
Summary: Run flaky test job more often
Key: HBASE-27425
URL: https://issues.apache.org/jira/browse/HBASE-27425
Project: HBase
Issue Type: Task
downstream issues due to Hadoop 3 being a non-default
> > build profile. (This could also be applied to all builds.)
> >
> > - Amend hbase-vote to be aware of and evaluate if present -hadoop3
> variant
> > artifacts.
> >
> >
> > > On Aug 25, 2022, a
[
https://issues.apache.org/jira/browse/HBASE-24457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-24457.
-
Fix Version/s: 3.0.0-alpha-1
(was: 3.0.0-alpha-4)
Resolution
yes, the flatten plugin. We use it in hbase-connectors already.
https://www.mojohaus.org/flatten-maven-plugin/
this sounds like it could also be a use case for BOMs, which would also
benefit users of our client artifacts that use build tools that don't
respect maven profiles generally, like
[
https://issues.apache.org/jira/browse/HBASE-26983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26983.
-
Resolution: Fixed
> Upgrade JRuby to 9.3.4.0
>
>
>
Sean Busbey created HBASE-27106:
---
Summary: HBase site generation should use its own JRuby
Key: HBASE-27106
URL: https://issues.apache.org/jira/browse/HBASE-27106
Project: HBase
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HBASE-26983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reopened HBASE-26983:
-
reopened to evaluate impact on site build
> Upgrade JRuby to 9.3.
[
https://issues.apache.org/jira/browse/HBASE-26983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26983.
-
Release Note:
Updates the version of JRuby that ships with HBase for the HBase shell
[
https://issues.apache.org/jira/browse/HBASE-27006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-27006.
-
Fix Version/s: 2.5.0
2.6.0
3.0.0-alpha-3
Sean Busbey created HBASE-27012:
---
Summary: nightly ITBLL
Key: HBASE-27012
URL: https://issues.apache.org/jira/browse/HBASE-27012
Project: HBase
Issue Type: Sub-task
Reporter: Sean
Sean Busbey created HBASE-27010:
---
Summary: container images for HBase
Key: HBASE-27010
URL: https://issues.apache.org/jira/browse/HBASE-27010
Project: HBase
Issue Type: Sub-task
Sean Busbey created HBASE-27011:
---
Summary: migrate existing nightly test
Key: HBASE-27011
URL: https://issues.apache.org/jira/browse/HBASE-27011
Project: HBase
Issue Type: Sub-task
Sean Busbey created HBASE-27009:
---
Summary: container images for ZooKeeper
Key: HBASE-27009
URL: https://issues.apache.org/jira/browse/HBASE-27009
Project: HBase
Issue Type: Sub-task
Sean Busbey created HBASE-27008:
---
Summary: container images for Hadoop
Key: HBASE-27008
URL: https://issues.apache.org/jira/browse/HBASE-27008
Project: HBase
Issue Type: Sub-task
Sean Busbey created HBASE-27007:
---
Summary: nightly support scripts for install/setup of single-node
k8s env
Key: HBASE-27007
URL: https://issues.apache.org/jira/browse/HBASE-27007
Project: HBase
Sean Busbey created HBASE-27006:
---
Summary: cordon off large ci worker nodes
Key: HBASE-27006
URL: https://issues.apache.org/jira/browse/HBASE-27006
Project: HBase
Issue Type: Sub-task
Sean Busbey created HBASE-27005:
---
Summary: move nightly cluster tests to run on k8s
Key: HBASE-27005
URL: https://issues.apache.org/jira/browse/HBASE-27005
Project: HBase
Issue Type: Umbrella
Sean Busbey created HBASE-26936:
---
Summary: project Jenkins node needs a fail-safe clean up of
surefire deferred output
Key: HBASE-26936
URL: https://issues.apache.org/jira/browse/HBASE-26936
Project
Sean Busbey created HBASE-26889:
---
Summary: nightly yetus tests don't reflect failure when required
environment variables are missing.
Key: HBASE-26889
URL: https://issues.apache.org/jira/browse/HBASE-26889
Sean Busbey created HBASE-26888:
---
Summary: Update branch-specific nightly test handling to allow for
earlier release line feature branches
Key: HBASE-26888
URL: https://issues.apache.org/jira/browse/HBASE-26888
Sean Busbey created HBASE-26887:
---
Summary: nightly integration test claims success while showing
error parsing shell output
Key: HBASE-26887
URL: https://issues.apache.org/jira/browse/HBASE-26887
Sorry for the lack of clarity. I meant to include that I’ll send the
message to the user list later today if folks don’t have a specific concern
with me doing so.
On Sat, Mar 19, 2022 at 9:03 AM Sean Busbey wrote:
> I think it’d be worth checking with user@ to see if there are continued
>
I think it’d be worth checking with user@ to see if there are continued
users of branch-1 that would be interested in getting more involved to keep
the branch going with eg dependency updates and security fixes should they
be needed.
On Fri, Mar 18, 2022 at 11:43 PM Viraj Jasani wrote:
> +1
Could someone translate the 2.3 EOM notice for the user-zh mailing list?
Longer term we should track a template that can get filled in for each of
the user lists so the poster needn’t be particularly proficient in either
language.
[
https://issues.apache.org/jira/browse/HBASE-26704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26704.
-
Resolution: Fixed
> EOL HBase 2.3.x
> ---
>
> Key:
Hi folks!
The Apache HBase 2.3 release line reached the end of maintenance in
October 2021. Our apologies for the late notification.
The final release was 2.3.7 and is available from archive.apache.org.
No further releases from branch-2.3 are planned.
Users of HBase 2.3.z should upgrade to the
would be nice.
>
> So I guess the next question is what does that require of us, the larger
> community. Who proposed the work? Who performs it? We should open some JIRAs
> to kick things off?
>
> > On Mar 10, 2022, at 8:32 AM, Sean Busbey wrote:
> >
> > H
Hi folks!
Quick background: all of the automated testing for nightly and PR
contributions is now running on a dedicated Jenkins instance (
ci-hbase.apache.org ). We moved our existing 10 dedicated nodes off of
the ci-hadoop controller and thanks to a new anonymous donor we were
able to add an
Sean Busbey created HBASE-26823:
---
Summary: ci-hbase expansion
Key: HBASE-26823
URL: https://issues.apache.org/jira/browse/HBASE-26823
Project: HBase
Issue Type: Task
Components
[
https://issues.apache.org/jira/browse/HBASE-26546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26546.
-
Resolution: Fixed
> hbase-shaded-client missing required thirdparty classes under hadoop 3.
so we would require a specific patch release of Hadoop as a minimum? It's
messy, but we've certainly done it before.
On Thu, Feb 17, 2022 at 1:31 PM Andrew Purtell wrote:
> On Thu, Feb 17, 2022 at 10:50 AM Steve Loughran wrote:
>
> > j
> > On 2022/02/15 22:27:50 Andrew Purtell wrote:
> >
> > >
Sean Busbey created HBASE-26760:
---
Summary: LICENSE handling should not allow non-aggregated
"apache-2.0"
Key: HBASE-26760
URL: https://issues.apache.org/jira/browse/HBASE-26760
Proj
[
https://issues.apache.org/jira/browse/HBASE-26696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26696.
-
Resolution: Fixed
this is all wrapped up now.
> Migrate our jenkins jobs from ci-hadoop to
[
https://issues.apache.org/jira/browse/HBASE-26756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26756.
-
Resolution: Fixed
went ahead and cleared things out.
> remove disabled hbase jobs from
Sean Busbey created HBASE-26758:
---
Summary: HBase Thirdparty repo should have nightly for checking
main repo tests on top of SNAPSHOT artifacts
Key: HBASE-26758
URL: https://issues.apache.org/jira/browse/HBASE-26758
es, I do not think it is time to fully drop
> the support of jdk8.
>
> Thanks.
>
> Sean Busbey 于2022年2月16日周三 09:57写道：
>
> > If we set the minJDK to 11 I believe that will effectively remove jdk8
> > support, rather than "just" deprecate it.
> >
> &
imary consideration to my mind is the state
> of S3A: in what version it can be said to be stable and feature complete. I
> think 3.3 is the appropriate code line for that criteria but perhaps 3.2
> could serve as well.
>
> > On Feb 15, 2022, at 10:48 AM, Sean Busbey wrote:
&
8 for HBase 3 and requiring minJdk=11 seems reasonable to
> me.
>
> Gotta start pushing the issue somehow.
>
> On 2/15/22 1:47 PM, Sean Busbey wrote:
> > Hi folks!
> >
> > It's been some time since we decided to stick to LTS JDK releases as a
> way
> > of getti
Hi folks!
It's been some time since we decided to stick to LTS JDK releases as a way
of getting a handle on the JDK treadmill.
What do folks think about deprecating JDK8? The openjdk8u project is still
going and there are commercial support options at least through 2030.
Deprecating it in HBase
Sean Busbey created HBASE-26756:
---
Summary: remove disabled hbase jobs from ci-hadoop
Key: HBASE-26756
URL: https://issues.apache.org/jira/browse/HBASE-26756
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-26740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26740.
-
Resolution: Fixed
I changed the job's label from {{arm2}} to {{arm}} after moving it to ci
Sean Busbey created HBASE-26755:
---
Summary: HBase website generation should show error details on
failure
Key: HBASE-26755
URL: https://issues.apache.org/jira/browse/HBASE-26755
Project: HBase
[
https://issues.apache.org/jira/browse/HBASE-26743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26743.
-
Resolution: Fixed
> migrate hbase-thirdparty
Sean Busbey created HBASE-26743:
---
Summary: migrate hbase-thirdparty PR
Key: HBASE-26743
URL: https://issues.apache.org/jira/browse/HBASE-26743
Project: HBase
Issue Type: Sub-task
Sean Busbey created HBASE-26740:
---
Summary: migrate ARM specific build
Key: HBASE-26740
URL: https://issues.apache.org/jira/browse/HBASE-26740
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-26737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26737.
-
Resolution: Fixed
looks good. got a failure and a success w/proper notification to github
Sean Busbey created HBASE-26737:
---
Summary: migrate hbase-native-client PR job
Key: HBASE-26737
URL: https://issues.apache.org/jira/browse/HBASE-26737
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-26736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26736.
-
Resolution: Fixed
> migrate hhbase-operator-tools PR
Sean Busbey created HBASE-26736:
---
Summary: migrate hhbase-operator-tools PR job
Key: HBASE-26736
URL: https://issues.apache.org/jira/browse/HBASE-26736
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-26735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26735.
-
Resolution: Fixed
> migrate hbase-connectors PR
Sean Busbey created HBASE-26735:
---
Summary: migrate hbase-connectors PR job
Key: HBASE-26735
URL: https://issues.apache.org/jira/browse/HBASE-26735
Project: HBase
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/HBASE-26698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26698.
-
Resolution: Fixed
> migrate website generat
[
https://issues.apache.org/jira/browse/HBASE-24936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-24936.
-
Assignee: Duo Zhang (was: Sean Busbey)
Resolution: Fixed
> review Jenkins bu
Sean Busbey created HBASE-26704:
---
Summary: EOL HBase 2.3.x
Key: HBASE-26704
URL: https://issues.apache.org/jira/browse/HBASE-26704
Project: HBase
Issue Type: Task
Components
Here's my +1.
That's 6 in favor and no other votes. I'll file an issue to track the clean
up work
On Sat, Jan 22, 2022 at 11:25 AM Peter Somogyi wrote:
> +1
>
> On Sat, Jan 22, 2022 at 6:22 PM Nick Dimiduk wrote:
>
> > +1
> >
> > On Fri, Jan 21, 2022 at 09:58 Se
n pre commit
> >>>> job for HBase are tied together. We need to move them at once.
> >>>>
> >>>> Gavin McDonald 于2022年1月22日周六 02:44写道：
> >>>>
> >>>>> Thanks for your patience
> >>>>>
> >>>>> I have 'co
know
>>>> if have any issues
>>>> with any other missing plugins.
>>>>
>>>>
>>>>
>>>> On Thu, Jan 20, 2022 at 1:11 PM 张铎(Duo Zhang)
>>>> wrote:
>>>>
>>>>> I’ve also replied on the jira issue.
>>>
Sean Busbey created HBASE-26698:
---
Summary: migrate website generation
Key: HBASE-26698
URL: https://issues.apache.org/jira/browse/HBASE-26698
Project: HBase
Issue Type: Sub-task
ion. We don’t investigate and
> attempt to manage the security reporting arrangement of any of our other
> third party dependencies.
>
> > On Jan 21, 2022, at 7:59 AM, Sean Busbey wrote:
> >
> > Has anyone asked the ASF Logging PMC if they'll forward security reports
>
Hi folks!
Discussion threads:
https://s.apache.org/i56se
https://s.apache.org/w1rit
tl;dr: we look to have consensus but missed formalizing things.
+1 for EOL?
ernal community action, is there a checklist for
> RMs to follow when a release line reaches end of life?
>
> Thanks,
> Nick
>
> On Thu, Jan 20, 2022 at 9:17 AM Andrew Purtell
> wrote:
>
> > Let’s vote. The stable pointer has been moved so there should be no
> ve
Has anyone asked the ASF Logging PMC if they'll forward security reports
against log4j 1 to the reload4j project?
On Fri, Jan 21, 2022 at 3:33 AM Pankaj Kumar wrote:
> +1 for reload4j.
>
> Regards,
> Pankaj
>
> On Fri, Jan 21, 2022, 2:39 PM 张铎(Duo Zhang) wrote:
>
> > Already filed HBASE-26691.
Hi folks!
Our Peter was asking in Slack about how to find the announcement for EOL on
HBase 2.3 releases. I did some digging around and I think there's been a
miscommunication.
The page header on our project's space on the ASF downloads page[1]
currently says 2.3 was EOL in October 2021. But
Hi Gavin
I went to start migrating jobs to the ci-hbase controller, but the new job
workflow doesn't include pipelines or multibranch pipelines. We use both of
these job types for nearly all of our work. Can they be enabled?
On Tue, Jan 18, 2022 at 5:04 AM Gavin McDonald wrote:
>
>
> On
I don't feel strongly about the specific proposal that started this thread.
I could see why someone might find it easier to skim the code; I don't feel
it impacts my reading personally. If there are folks with differing
opinions over it; my preference would be that we stick with whatever style
is
2.4 version of the book and honestly I haven't found time to
> > do it, because it seems both low priority and nontrivial, and there's never
> > enough time for everything... although that may be a personal failing.
> >
> > On Fri, Jan 7, 2022 at 9:05 AM Sean Busbey
We should have a version specific version of the ref guide that
contains that information.
e.g.
https://hbase.apache.org/1.4/book.html#hadoop
https://hbase.apache.org/2.3/book.html#hadoop
Can we do a better job of making these discoverable to folks rather
than keeping stuff around?
On Fri,
If we don't want to wait for HBASE-26543 (fix arg parsing for shell)
then we should revert HBASE-24772 from branch-2.5 prior to an RC.
On Wed, Dec 8, 2021 at 7:34 PM Andrew Purtell wrote:
>
> As your branch-2.5 RM I am assembling a list of work items that should be
> completed before a 2.5.0RC0
That'd be great!
I can help with release process.
I'd like us to ensure this go around we have convenience binaries compiled
against Spark 3 as well. That's been a long standing need.
On Mon, Dec 6, 2021, 16:43 Tak Lon (Stephen) Wu wrote:
> Hi guys,
>
> While I'm learning how to release a
Sean Busbey created HBASE-26543:
---
Summary: HBase shell no longer properly parses several args
Key: HBASE-26543
URL: https://issues.apache.org/jira/browse/HBASE-26543
Project: HBase
Issue Type
Sean Busbey created HBASE-26469:
---
Summary: HBase shell has changed exit behavior
Key: HBASE-26469
URL: https://issues.apache.org/jira/browse/HBASE-26469
Project: HBase
Issue Type: Bug
If it was akin to slf4j, that integration has been relatively smooth
for downstream.
log4j effectively being in our public api through configuration
formats has been a maintenance nightmare.
These would effectively be in our java binary API though, right? Would
we gain any meaningful isolation
for example, this is roughly what HBase 2.4.7 would look like:
https://gist.github.com/busbey/b5a849626bc4fcc2cbdd18f56c8d2807#file-apache-hbase-2-4-7-releasenotes-md
(but the url would be to the rel/2.4.7 tag on github)
On Tue, Oct 26, 2021 at 1:33 PM Sean Busbey wrote:
> let's just st
our announcements point people at something that
> requires a login. It seems not very “open” or “inviting”.
>
> On Tue, Oct 26, 2021 at 07:26 Sean Busbey wrote:
>
> > We have historically linked to the Jira Version page because it provides
> a
> > starting point on issue navigati
We have historically linked to the Jira Version page because it provides a
starting point on issue navigation that we don't get elsewhere. Plenty of
interactions with our issue tracker require a login. Why is that threshold
not acceptable here? I think we should just note that a login with
k to the docker build issue, is it possible to push the docker image
> to docker hub so we do not need to build it every time when the cache
> expires?
>
> I saw there is an 'apache' user on docker hub...
>
> https://hub.docker.com/u/apache
>
> Thanks.
>
> Sean Busbey
the help in making it easier to use the hadoop-connectors for
> Spark 3. Keep me posted if there's any additional information needed.
>
> regards,
> Jordan
>
> On 2021/10/08 16:09:34, Sean Busbey wrote:
> > Hi Jordan!
> >
> > How do you currently pull in the de
Hi folks!
I'd like us to move the stable pointer from 2.3.z releases to 2.4.6+ releases.
The last time we talked about doing so[1] there was a desire to get
some documentation together on what we as a community expect from the
"stable" release line. We have an issue tracking those needs[2], but
it could be that the curl in the docker image for branch-1 is older and is
missing some newer CAs.
Could we sidestep this issue by installing tooling from spotbugs instead?
On Fri, Oct 8, 2021 at 10:54 PM 张铎(Duo Zhang) wrote:
> They all fail with docker image building failure.
>
> 10:50:04
Hi Jordan!
How do you currently pull in the dependency? Do you need us to publish an
artifact to maven central? Would a convenience binary built against spark-3
on downloads.apache.org suffice?
On Thu, Oct 7, 2021 at 7:55 PM Jordan Hambleton
wrote:
> Hi Peter,
>
> We're seeing an uptick in
please start a dedicated DISCUSS thread about moving the stable pointer.
On Thu, Oct 7, 2021 at 11:33 PM Yu Li wrote:
> Hi all,
>
> Since 2.4.6 has been released on Sep. 13th and we plan to EOL 2.3.x, shall
> we move the stable pointer to 2.4 (it's still on 2.3.6 for now on our
> download page
Sean Busbey created HBASE-26332:
---
Summary: Update next set of minor releases for Hadoop 3.1 EOM
Key: HBASE-26332
URL: https://issues.apache.org/jira/browse/HBASE-26332
Project: HBase
Issue
Sean Busbey created HBASE-26331:
---
Summary: verify hbase testing infra is up to date wrt H node
renaming
Key: HBASE-26331
URL: https://issues.apache.org/jira/browse/HBASE-26331
Project: HBase
t; > > > hbase.thrift file, that thbase used, in the repo. In this case, repo
> > > > separation will lead to a sync problem between the hbase.thrfit files
> > in
> > > > HBase repo and the connector repo. I am concerned this may make it hard
> > >
Hi!
Heads up that a discussion has started in Apache Yetus about dropping
the Audience Annotations and associated javadoc tooling due to lack of
community support[1]. The current cutting issue AFAICT is that things
there haven't been updated for the changes in how doclets are handled
in JDK9+.
Our API is already too big to audit by hand for breakage. The limited
tooling we have for automatically scanning as a part of the release
process[1] only has the ability to cope with a single set of
annotation (i.e. it can do "filter to things that are IA.Public" and
it can't do "filter to things
maybe a good fit for the hbase-connectors repo? I know we've talked a
few times about moving the thrift server out there. if we did both
then the compatibility question becomes just the standard
client/server compatibility provided the thrift server only uses our
public java client API.
On Thu,
[
https://issues.apache.org/jira/browse/HBASE-26031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-26031.
-
Resolution: Later
After chatting with Stack about donation internals, these hosts are getting
Sean Busbey created HBASE-26031:
---
Summary: Validate nightly builds run on new ci workers
hbase10-hbase15
Key: HBASE-26031
URL: https://issues.apache.org/jira/browse/HBASE-26031
Project: HBase
added!
On Thu, May 27, 2021 at 2:13 PM Reid Chan wrote:
>
> Hi team,
>
> I'm working on the hbase-1.7.0 release, but found I couldn't add a new tag
> for unreleased versions, could someone grant me the access?
>
> Thanks.
>
> ---
> Best Regards,
> R.C
I'm happy to see us moving forward with hbase 3 release.
If a feature makes it into alpha releases but under evaluation doesn't look
ready for use, what's the plan? Back things out and put it into a feature
branch?
What about making releases out of the master branch until we stabilize the
API by
My understanding is that backup work is not ready for inclusion in 2.x.
The talk of removing it from the master branch and proposed adoption of the
feature through more involvement from some community members were not so
long ago.
On Tue, May 4, 2021, 15:49 Andrew Purtell wrote:
> Correct me
[
https://issues.apache.org/jira/browse/HBASE-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-2.
-
Resolution: Fixed
> release hbase-thirdparty 3.
We've just made a new release of the Apache HBase Thirdparty project.
This project is used by the Apache HBase project to encapsulate a
number of core dependencies that HBase relies upon ensuring
that they are properly isolated from HBase downstream users, e.g.
Google Protocol Buffers, Google
The HBase team is happy to announce the immediate availability of Apache
HBase Operator Tools 1.1.0.
Apache HBase™ Operator Tools provides HBCK2 which is the repair tool for
Apache HBase 2 clusters.
To learn more about HBase and HBase Operator Tools, see
https://hbase.apache.org/.
The full list
Sean Busbey created HBASE-25589:
---
Summary: release hbase-operator-tools 1.1.0
Key: HBASE-25589
URL: https://issues.apache.org/jira/browse/HBASE-25589
Project: HBase
Issue Type: Task
With three +1s and no other votes, this release passes as Apache HBase
Operator Tools 1.1.0.
Thanks y'all for voting!
On Sat, Feb 13, 2021 at 12:32 PM Sean Busbey wrote:
>
> Please vote on this Apache hbase operator tools release candidate,
> hbase-operator-tools-1.1.0RC0
>
1.8.0_242): ok
> > - mvn clean install -DskipTests
> > * Unit tests pass (1.8.0_242): ok
> > - mvn package -P runAllTests -Dsurefire.rerunFailingTestsCount=3
> >
> > Built hbase master branch with hbase-thirdparty:3.5.0 dependency, executed
Sean Busbey created HBASE-25580:
---
Summary: Release scripts should include in the vote email the git
hash that the RC tag points to
Key: HBASE-25580
URL: https://issues.apache.org/jira/browse/HBASE-25580
1 - 100 of 2323 matches
Mail list logo
