hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Wang <andrew.w...@cloudera.com>
Subject Re: Release numbering for 3.x leading up to GA
Date Thu, 12 May 2016 17:52:59 GMT
Hi all,

Sounds like we have general agreement on this release numbering scheme for

I'm going to attempt some mvn and JIRA invocations to get the version
numbers lined up for alpha1, wish me luck.


On Tue, May 3, 2016 at 9:52 AM, Roman Shaposhnik <roman@shaposhnik.org>

> On Tue, May 3, 2016 at 8:18 AM, Karthik Kambatla <kasha@cloudera.com>
> wrote:
> > The naming scheme sounds good. Since we want to start out sooner, I am
> > assuming we are not limiting ourselves to two alphas as the email might
> > indicate.
> >
> > Also, as the release manager, can you elaborate on your definitions of
> > alpha and beta? Specifically, when do we expect downstream projects to
> try
> > and integrate and when we expect Hadoop users to try out the bits?
> Not to speak of all the downstream PMC,s but Bigtop project will jump
> on the first alpha the same way we jumped on the first alpha back
> in the 1 -> 2 transition period.
> Given that Bigtop currently integrates quite a bit of Hadoop ecosystem
> that work is going to produce valuable feedback that we plan to communicate
> to the individual PMCs. What PMCs do with that feedback, of course, will
> be up to them (obviously Bigtop can't take the ownership of issues that
> go outside of integration work between projects in the Hadoop ecoystem).
> Thanks,
> Roman.

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