Thanks Andrew. I also had a talk with Kai offline. Agreed that we should try our best to finalize coder config changes for alpha1.
On Tue, May 17, 2016 at 5:34 PM Andrew Wang <andrew.w...@cloudera.com> wrote: > The sooner the better for incompatible changes, but at this point we are > explicitly not guaranteeing any compatibility between alpha releases. > > For EC, my understanding is that we're still working on the coder > configuration. Given that we're still working on L&N changes, I think it's > possible that the coder configuration will be finished in time. > > On Tue, May 17, 2016 at 4:42 PM, Zhe Zhang <zhe.zhang.resea...@gmail.com> > wrote: > > > Naming convention looks good. Thanks Andrew for driving this! > > > > Could you explain a little more on the criteria of cutting alpha1 / > > alpha2? What are the goals we want to achieve for alpha1? From EC's > > perspective, maybe we should target on having all compatibility-related > > changes in alpha1, like new config keys and fsimage format? > > > > Thanks, > > > > On Thu, May 12, 2016 at 11:35 AM Andrew Wang <andrew.w...@cloudera.com> > > wrote: > > > >> Hi folks, > >> > >> I think it's working, though it takes some time for the rename to > >> propagate > >> in JIRA. JIRA is also currently being hammered by spammers, which might > be > >> related. > >> > >> Anyway, the new "3.0.0-alpha1" version should be live for all four > >> subprojects, so have at it! > >> > >> Best, > >> Andrew > >> > >> On Thu, May 12, 2016 at 11:01 AM, Gangumalla, Uma < > >> uma.ganguma...@intel.com> > >> wrote: > >> > >> > Thanks Andrew for driving. Sounds good. Go ahead please. > >> > > >> > Good luck :-) > >> > > >> > Regards, > >> > Uma > >> > > >> > On 5/12/16, 10:52 AM, "Andrew Wang" <andrew.w...@cloudera.com> wrote: > >> > > >> > >Hi all, > >> > > > >> > >Sounds like we have general agreement on this release numbering > scheme > >> for > >> > >3.x. > >> > > > >> > >I'm going to attempt some mvn and JIRA invocations to get the version > >> > >numbers lined up for alpha1, wish me luck. > >> > > > >> > >Best, > >> > >Andrew > >> > > > >> > >On Tue, May 3, 2016 at 9:52 AM, Roman Shaposhnik < > ro...@shaposhnik.org > >> > > >> > >wrote: > >> > > > >> > >> On Tue, May 3, 2016 at 8:18 AM, Karthik Kambatla < > ka...@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. > >> > >> > >> > > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > >> > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > >> > > >> > > >> > > -- > > Zhe Zhang > > Apache Hadoop Committer > > http://zhe-thoughts.github.io/about/ | @oldcap > > > -- Zhe Zhang Apache Hadoop Committer http://zhe-thoughts.github.io/about/ | @oldcap
