We need clarification on this then. I was under the impression that branch-2 would be 2.2.0.
thx On Tue, Jul 2, 2013 at 2:38 PM, Jason Lowe <jl...@yahoo-inc.com> wrote: > I thought Arun intends for 2.2.0 to be created off of branch-2.1.0-beta > and not off of branch-2. As I understand it, only critical blockers will > be the delta between 2.1.0-beta and 2.2.0 and items checked into branch-2 > should be marked as fixed in 2.3.0. > > Part of the confusion is that currently branch-2 builds as 2.2.0-SNAPSHOT, > but I believe Arun intended it to be 2.3.0-SNAPSHOT. > > Jason > > > On 06/21/2013 12:05 PM, Alejandro Abdelnur wrote: > >> Thanks Suresh, didn't know that, will do. >> >> >> On Fri, Jun 21, 2013 at 9:48 AM, Suresh Srinivas <sur...@hortonworks.com >> >wrote: >> >> I have added in to HDFS, HADOOP, MAPREDUCE projects. Can someone add it >>> for >>> YARN? >>> >>> >>> On Fri, Jun 21, 2013 at 9:35 AM, Alejandro Abdelnur <t...@cloudera.com >>> >>>> wrote: >>>> When Arun created branch-2.1-beta he stated: >>>> >>>> The expectation is that 2.2.0 will be limited to content in >>>>> >>>> branch-2.1-beta >>>> >>>>> and we stick to stabilizing it henceforth (I've deliberately not >>>>> >>>> created >>> >>>> 2.2.0 >>>> >>>>> fix-version on jira yet). >>>>> >>>> I working/committing some JIRAs that I'm putting in branch-2 (testcases >>>> >>> and >>> >>>> improvements) but I don't want to put them in branch-2.1-beta as they >>>> are >>>> not critical and I don't won't add unnecessary noise to the >>>> >>> branch-2.1-beta >>> >>>> release work. >>>> >>>> Currently branch-2 POMs have a version 2.2.0 and the CHANGES.txt files >>>> as >>>> well. >>>> >>>> But because we did not create a JIRA version I cannot close those JIRAs. >>>> >>>> Can we please create the JIRA versions? later we can rename them. >>>> >>>> Thx >>>> >>>> >>>> -- >>>> Alejandro >>>> >>>> >>> >>> -- >>> http://hortonworks.com/**download/ <http://hortonworks.com/download/> >>> >>> >> >> > -- Alejandro
