I followed up with Apple and I think he's positioned to get things done. I'll leave the timing up to him.
That said, I am already on progress on 1.2.7. currently RCs for that release are blocked on getting nightly tests that pass again. On Nov 15, 2017 10:54, "Nick Dimiduk" <[email protected]> wrote: > Sean, > > Do you have a target date you'd like to see the community aiming for on > this one? > > If you don't mind, I would propose the Release Wrangler get started in JIRA > pruning and test suite kicking over the next couple weeks, and we can > target the first or second week of Dec. There's been quite a few commits > since the last release, so there may be some surprises lurking for our > volunteers to sort out. A good place to start is the compatibility report. > > Who will carry this banner? Apekshit, Jan: shall we draw straws? One of you > have a bit of extra free time over the next 4 weeks? > > Thanks, > Nick > > On Wed, Nov 1, 2017 at 11:33 AM Jan Hentschel < > [email protected]> wrote: > > > I also like to volunteer, but I don’t think that I can do it on my own. > > > > > > > > Jan > > > > > > > > From: Apekshit Sharma <[email protected]> > > Reply-To: <[email protected]> > > Date: Wednesday, November 1, 2017 at 12:24 AM > > To: <[email protected]> > > Subject: Re: [DISCUSS] Any committers willing to do maintenance releases > > over the holidays? > > > > > > > > Loads of helping hands...woohoo! > > > > > > > > -Appy > > > > > > > > > > > > On Oct 31, 2017 4:01 PM, "Nick Dimiduk" <[email protected]> wrote: > > > > > > > > As 1.1 is rounding down, I will be able to apply that time to helping out > > > > on another release line, if that's useful to the community. > > > > > > > > Thanks, > > > > Nick > > > > > > > > On Mon, Oct 30, 2017 at 9:35 PM, Sean Busbey <[email protected]> wrote: > > > > > > > > > Hi folks! > > > > > > > > > > I'm in the process of getting us a 1.2.7-RC, hopefully soon[1]. This > > > > > release is badly behind schedule. I'd very much like to get us back on > > > > > a regular cadence for our stable release line, with a goal of once a > > > > > month. Unfortunately, I'm very unlikely to have time to do release > > > > > managing after the 1.2.7 release until spring (luckily it's for > > > > > fortunate-to-me reasons). > > > > > > > > > > Despite the delay in schedule on this release, generally doing a > > > > > maintenance release is relatively low effort. These kinds of > > > > > "substitute RM" situations are a great chance to get familiar with the > > > > > process while having a well-defined end point. If there's anyone who'd > > > > > like to give it a try by handling things while I'm gone, both I and > > > > > I'm sure the project community would be grateful. > > > > > > > > > > To take on this particular task, one must be a committer already (due > > > > > to ASF policy). It's a great way to "act like a PMC" for those > > > > > committers who'd like to make a long term investment in HBase. > > > > > > > > > > Anyone interested? > > > > > > > > > > -busbey > > > > > > > > > > [1]: https://issues.apache.org/jira/browse/HBASE-18276 > > > > > > > > > > > > > > > > > >
