hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Hentschel <jan.hentsc...@ultratendency.com>
Subject Re: [DISCUSS] Any committers willing to do maintenance releases over the holidays?
Date Wed, 01 Nov 2017 18:33:21 GMT
I also like to volunteer, but I don’t think that I can do it on my own.




From: Apekshit Sharma <appy@cloudera.com>
Reply-To: <dev@hbase.apache.org>
Date: Wednesday, November 1, 2017 at 12:24 AM
To: <dev@hbase.apache.org>
Subject: Re: [DISCUSS] Any committers willing to do maintenance releases over the holidays?


Loads of helping hands...woohoo!





On Oct 31, 2017 4:01 PM, "Nick Dimiduk" <ndimiduk@gmail.com> 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.





On Mon, Oct 30, 2017 at 9:35 PM, Sean Busbey <busbey@apache.org> 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




  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message