So are we saying a) RC in regards to an official Apache VOTE and keeping it open for week(s) and continuously patching as issues come up calling more RC VOTEs until we ship?
b) instead of beta name the release RC1 so in Maven Central it would be 0.8.2-RC1 and we could have RCX votes for that? If we went with a) folks could use the artifacts staged in apache release repository so technically possible to-do. I am in favor with which ever folks would be most likely to start to push and/or finally push into production prior to final. /******************************************* Joe Stein Founder, Principal Consultant Big Data Open Source Security LLC http://www.stealth.ly Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> ********************************************/ On Mon, Jan 12, 2015 at 12:26 PM, Neha Narkhede <n...@confluent.io> wrote: > Joe, > > Thanks for starting the discussion. It may be ok to do an RC and probably > two weeks later, cut the final. After releasing the RC, we can help spread > the word and have people try out the new API, which is probably our main > concern. > > -Neha > > On Mon, Jan 12, 2015 at 8:42 AM, Jun Rao <j...@confluent.io> wrote: > > > Hi, Joe, > > > > Yes, we can do that. > > > > Also, an alternative to doing an 0.8.2 beta2 is to just do the 0.8.2 > final, > > but leave a bit more time for people to try the RC. > > > > Thanks, > > > > Jun > > > > On Thu, Jan 8, 2015 at 8:46 PM, Joe Stein <joe.st...@stealth.ly> wrote: > > > > > Hi, I was thinking that once all the blockers are committed for 0.8.2 > > that > > > we should release beta2. > > > > > > Thoughts? > > > > > > /******************************************* > > > Joe Stein > > > Founder, Principal Consultant > > > Big Data Open Source Security LLC > > > http://www.stealth.ly > > > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > > > ********************************************/ > > > > > > > > > -- > Thanks, > Neha >
