On Wed, Jun 7, 2017 at 2:31 PM, Stack <st...@duboce.net> wrote: > On Wed, Jun 7, 2017 at 11:13 AM, Andrew Purtell <apurt...@apache.org> wrote: > >> Thanks. >> I'd like to see us RM branch-2, branch-1, and master and get away from >> narrow focus on the branch-x.y branches that only produce patch releases. >> Seems a better use of RM bandwidth to supervise a whole code line. >> >> > I like this idea. Lets try it. > > Related, I just published 2.0.0-SNAPSHOT cut from branch-2. I'm thinking of > just putting this up as RC for 2.0.0-alpha1. Any objections? Would be good > to have something up even if it has wrong hadoop, wrong libs, is in > complete, etc. > > St.Ack
So long as we're consistent in messaging to downstream, sounds good to me. Addressable artifacts would let me e.g. update hbase-downstreamer and ycsb, which would make testing easier.
