On Tue, Oct 1, 2013 at 8:59 PM, Arun C Murthy <a...@hortonworks.com> wrote: > Yes, sorry if it wasn't clear. > > As others seem to agree, I think we'll be better getting a protocol/api > stable GA done and then iterating on bugs etc. > > I'm not super worried about HADOOP-9984 since symlinks just made it to > branch-2.1 recently. > > Currently we only have 2 blockers: HADOOP-9984 & MAPREDUCE-5530. Both of > which are PA and I've reviewed MR-5530 and is good to go (thanks Robert). > Hopefully we can finish up HADOOP-9984 asap and we'll be good.
We've had several reviews for HADOOP-9984 and are currently just waiting on a +1. Sorry if this is a dumb question, but will the 2.2 release be made from branch-2 or what is currently named branch-2.1-beta? If it is the latter, we have a few backports we'll need to do. Colin > > thanks, > Arun > > On Oct 1, 2013, at 4:53 PM, Alejandro Abdelnur <t...@cloudera.com> wrote: > >> Arun, >> >> Does this mean that you want to skip a beta release and go straight to GA >> with the next release? >> >> thx >> >> >> On Tue, Oct 1, 2013 at 4:15 PM, Arun C Murthy <a...@hortonworks.com> wrote: >> >>> Guys, >>> >>> I took a look at the content in 2.1.2-beta so far, other than the >>> critical fixes such as HADOOP-9984 (symlinks) and few others in YARN/MR, >>> there is fairly little content (unit tests fixes etc.) >>> >>> Furthermore, it's standing up well in testing too. Plus, the protocols >>> look good for now (I wrote a gohadoop to try convince myself), let's lock >>> them in. >>> >>> Given that, I'm thinking we can just go ahead rename it 2.2.0 rather than >>> make another 2.1.x release. >>> >>> This will drop a short-lived release (2.1.2) and help us move forward on >>> 2.3 which has a fair bunch of content already... >>> >>> Thoughts? >>> >>> thanks, >>> Arun >>> >>> >>> On Sep 24, 2013, at 4:24 PM, Zhijie Shen <zs...@hortonworks.com> wrote: >>> >>>> I've added MAPREDUCE-5531 to the blocker list. - Zhijie >>>> >>>> >>>> On Tue, Sep 24, 2013 at 3:41 PM, Arun C Murthy <a...@hortonworks.com> >>> wrote: >>>> >>>>> With 4 +1s (3 binding) and no -1s the vote passes. I'll push it out… >>> I'll >>>>> make it clear on the release page, that there are some known issues and >>>>> that we will follow up very shortly with another release. >>>>> >>>>> Meanwhile, let's fix the remaining blockers (please mark them as such >>> with >>>>> Target Version 2.1.2-beta). >>>>> The current blockers are here: >>>>> http://s.apache.org/hadoop-2.1.2-beta-blockers >>>>> >>>>> thanks, >>>>> Arun >>>>> >>>>> On Sep 16, 2013, at 11:38 PM, Arun C Murthy <a...@hortonworks.com> >>> wrote: >>>>> >>>>>> Folks, >>>>>> >>>>>> I've created a release candidate (rc0) for hadoop-2.1.1-beta that I >>>>> would like to get released - this release fixes a number of bugs on top >>> of >>>>> hadoop-2.1.0-beta as a result of significant amounts of testing. >>>>>> >>>>>> If things go well, this might be the last of the *beta* releases of >>>>> hadoop-2.x. >>>>>> >>>>>> The RC is available at: >>>>> http://people.apache.org/~acmurthy/hadoop-2.1.1-beta-rc0 >>>>>> The RC tag in svn is here: >>>>> >>> http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.1-beta-rc0 >>>>>> >>>>>> The maven artifacts are available via repository.apache.org. >>>>>> >>>>>> Please try the release and vote; the vote will run for the usual 7 >>> days. >>>>>> >>>>>> thanks, >>>>>> Arun >>>>>> >>>>>> >>>>>> -- >>>>>> Arun C. Murthy >>>>>> Hortonworks Inc. >>>>>> http://hortonworks.com/ >>>>>> >>>>>> >>>>> >>>>> -- >>>>> Arun C. Murthy >>>>> Hortonworks Inc. >>>>> http://hortonworks.com/ >>>>> >>>>> >>>>> >>>>> -- >>>>> CONFIDENTIALITY NOTICE >>>>> NOTICE: This message is intended for the use of the individual or >>> entity to >>>>> which it is addressed and may contain information that is confidential, >>>>> privileged and exempt from disclosure under applicable law. If the >>> reader >>>>> of this message is not the intended recipient, you are hereby notified >>> that >>>>> any printing, copying, dissemination, distribution, disclosure or >>>>> forwarding of this communication is strictly prohibited. If you have >>>>> received this communication in error, please contact the sender >>> immediately >>>>> and delete it from your system. Thank You. >>>>> >>>> >>>> >>>> >>>> -- >>>> Zhijie Shen >>>> Hortonworks Inc. >>>> http://hortonworks.com/ >>>> >>>> -- >>>> CONFIDENTIALITY NOTICE >>>> NOTICE: This message is intended for the use of the individual or entity >>> to >>>> which it is addressed and may contain information that is confidential, >>>> privileged and exempt from disclosure under applicable law. If the reader >>>> of this message is not the intended recipient, you are hereby notified >>> that >>>> any printing, copying, dissemination, distribution, disclosure or >>>> forwarding of this communication is strictly prohibited. If you have >>>> received this communication in error, please contact the sender >>> immediately >>>> and delete it from your system. Thank You. >>> >>> -- >>> Arun C. Murthy >>> Hortonworks Inc. >>> http://hortonworks.com/ >>> >>> >>> >>> -- >>> CONFIDENTIALITY NOTICE >>> NOTICE: This message is intended for the use of the individual or entity to >>> which it is addressed and may contain information that is confidential, >>> privileged and exempt from disclosure under applicable law. If the reader >>> of this message is not the intended recipient, you are hereby notified that >>> any printing, copying, dissemination, distribution, disclosure or >>> forwarding of this communication is strictly prohibited. If you have >>> received this communication in error, please contact the sender immediately >>> and delete it from your system. Thank You. >>> >> >> >> >> -- >> Alejandro > > -- > Arun C. Murthy > Hortonworks Inc. > http://hortonworks.com/ > > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You.
