Thanks for driving this, Andrew. Sounds great. >> but I'm going to spend time on our first RC this week. Sorry what does this mean? Did you mean the first RC version or 3.0.0-alpha1 will be cut out this week? Anyway will try to get some tasks done sooner.
Regards, Kai -----Original Message----- From: Andrew Wang [mailto:andrew.w...@cloudera.com] Sent: Tuesday, May 03, 2016 5:07 AM To: Roman Shaposhnik <ro...@shaposhnik.org> Cc: common-dev@hadoop.apache.org Subject: Re: Release numbering for 3.x leading up to GA On Mon, May 2, 2016 at 2:00 PM, Roman Shaposhnik <ro...@shaposhnik.org> wrote: > On Mon, May 2, 2016 at 1:50 PM, Andrew Wang <andrew.w...@cloudera.com> > wrote: > > Hi all, > > > > I wanted to confirm my version numbering plan for Hadoop 3.x. We had > > a related thread on this topic about a year ago, mostly focusing on > > the > > branch-2 maintenance releases: > > > > > http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201504.mbox > /%3CFAA30A53-C2BD-4380-9245-C8DBEC7BF386%40hortonworks.com%3E > > > > For Hadoop 3, I wanted to do something like scheme (2) in Vinod's > original > > email from the above thread. e.g. leading up to GA, we'd have: > > > > 3.0.0-alpha1 > > 3.0.0-alpha2 > > 3.0.0-beta1 > > 3.0.0 > > +1 on the naming scheme. Also (and I know this is an impossible > question to answer, but still) > what are the rough timing expectations on these? > > Thanks Roman. Regarding release timing, this is what we discussed on another thread: > For exit criteria, how about we time box it? My plan was to do monthly alphas through the summer, leading up to beta in late August / early Sep. At that point we freeze and stabilize for GA in Nov/Dec. As you say, release plans need to be flexibly, but I'm going to spend time on our first RC this week.
