Hello everyone, An update here is well overdue. There's a lot of progress that's been made over the last 6 weeks. We've seen a number of new features wrapped up and land on branch-2, and a lot of effort has been done to prune and weed our garden of unruly unit tests. We've also had a number of healthy discussions, about our release process as well as our minimum Hadoop version. I would still like to see our unit test suite running on JDK11, which is an effort I will continue to pursue as I'm able (subtasks of HBASE-22972).
I think we're finally ready to make branch-2.3. Once the branch is live, I ask that folks pause actively backporting new features to branch-2.3. Please continue with bug fixes. There is at least one data correctness issue of which I am aware (HBASE-23286). Patches that improve and stabilize our test suite are also strongly encouraged. We've seen stray blue nightlies, but not often and not recently. If you're looking for direction in this area, search Jira for "flakey" or ping me or Stack on Slack. The GitHub PR PreCommit job now archives test logs, so it is now easier to retrieve high fidelity details from runs on Apache infrastructure. If you have concerns or objections, please raise them here. If there are specific bugs you'd like me to track, please let me know. Otherwise, I'll push the branch on Monday, start building a changes list and learning the release tools. Thank you everyone for your contributions and hard work. Nick On Mon, Jan 27, 2020 at 4:49 PM Nick Dimiduk <ndimi...@apache.org> wrote: > Heya, > > I wanted to give an update on progress toward the first 2.3.0 RCs. > > Jira has been cleaned up, with a bunch of unlikely tickets kicked out. > FixVersions have also been audited to ensure they match what's in git. On > first glance, this is shaping up to be a fat release, with over 800 issues > in this version [0]. However, it's not quite as scary as all that. I was > able to assemble a report of only the issues that are new to this version, > tickets that have not seen a previous release [1]. This list is shorter, > only about 175 currently, and when it's all said and done, I expect we'll > land in somewhere on the order of 200. > > There are yet a few major tickets to land before the release branch is > cut. The two bigger feature work items that I have my eyes on > are HBASE-18095 and HBASE-22978. I've also marked HBASE-22972 as a > blocker. If you have other new feature work you're hoping to get into > 2.3.0, please set the fixVersion and ping me in the comments or your PR. If > you have some spare cycles, please take a pass through our open PR's [2]; > there's quite a bit of low-hanging fruit in there that could use some > attention. > > Our test situation is still looking a bit rough [3]. A couple brave souls > have started working through the flakies [4], but there's more work to be > done. > > That's where we're at. With this amount of work, I expect that puts the > first RC sometime the week of Feb 10 or Feb 17. If folks want binaries they > can start to abuse before then, let me know and I'll see what can be done. > > That's what I have for today. Please speak up with questions and concerns. > Preemptive thank you to everyone who's been pushing to bring this release > together. Your work has not gone unnoticed. > > Thanks, > Nick > > [0]: https://issues.apache.org/jira/projects/HBASE/versions/12344893 > [1]: http://home.apache.org/~ndimiduk/new_for_branch-2.csv > [2]: https://github.com/apache/hbase/pulls > [3]: > https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/branch-2/ > [4]: > https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/job/branch-2/lastSuccessfulBuild/artifact/dashboard.html >
