[ https://issues.apache.org/jira/browse/HBASE-22956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929549#comment-16929549 ]
stack commented on HBASE-22956: ------------------------------- Did compare of git to JIRA manually. hbase-operator-tools is ready to go [~psomogyi] if you want to run the release sir (IMO). See what you think. To make the RC, hopefully you just type ./dev-support/create-release/do-release-docker.sh (after ensuring a local docker is up), answer a few questions, and then a release candidate pops out the other end (~40minutes). Shout if doesn't make sense. > [HBCK2/hbase-operator-tools] Make first release, 1.0.0 > ------------------------------------------------------ > > Key: HBASE-22956 > URL: https://issues.apache.org/jira/browse/HBASE-22956 > Project: HBase > Issue Type: Bug > Components: hbck2 > Reporter: stack > Priority: Major > > Make our first release of hbck2/hbase-operator-tools. > First release should have the coverage hbck1 had at least. When the parent > for this issue is done, we'll be at hbck1+. Let us release then (week or > two?). > A release will help operators who have been struggling having to build hbck2 > against different hbase versions. The release should be a "fat > jar"/completely contained with all dependency satisfied so operator can just > fire up hbck2 w/o having to build against an hbase or provide some magic mix > of jars to satisfy hbck2 tool needs. -- This message was sent by Atlassian Jira (v8.3.2#803003)