Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of ndimiduk@gmail.com designates
 209.85.128.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1365096783.48709.YahooMailNeo@web140603.mail.bf1.yahoo.com>
References: 
 <CAAha9a2SBPduOWGfHJdzfac2_WrfhvAeQP92NNZAbWffCeRAYw@mail.gmail.com>
 <1365095403.68604.YahooMailNeo@web140604.mail.bf1.yahoo.com>
 <CAAha9a3FEP4jZKXhgf2VvXzYsH6Zv1B6CCC5bHhz9kDOeSrfyQ@mail.gmail.com>
 <1365096783.48709.YahooMailNeo@web140603.mail.bf1.yahoo.com>
From: Nick Dimiduk <ndimiduk@gmail.com>
Date: Thu, 4 Apr 2013 11:55:56 -0700
Message-ID: 
 <CANZa=Gvo6HmDaZ272wWXfDwfwrfAWHZ8ywcTELPFuoL5wotGbg@mail.gmail.com>
Subject: Re: Marking fix version
To: dev@hbase.apache.org, lars hofhansl <larsh@apache.org>
Content-Type: multipart/alternative; boundary=bcaec51ddd49798c6904d98d86cf

--bcaec51ddd49798c6904d98d86cf
Content-Type: text/plain; charset=UTF-8

By this logic, 0.98 tag should be renamed to 0.97, yes?

On Thu, Apr 4, 2013 at 10:33 AM, lars hofhansl <larsh@apache.org> wrote:

> Yes, I think we should remove the 0.96 tag. Stack said the other day that
> he should have just renamed 0.96 to 0.95 rather than moving all the issues.
>
> The rest is already what I have been doing for issues I am committing (so
> +1 :) ), but I did notice that not all issues are tagged correctly.
>
>
> -- Lars
>
>
>
> ________________________________
>  From: Jonathan Hsieh <jon@cloudera.com>
> To: dev@hbase.apache.org; lars hofhansl <larsh@apache.org>
> Sent: Thursday, April 4, 2013 10:15 AM
> Subject: Re: Marking fix version
>
>
> The argument for excluding the 0.96 tag makes sense.  Can we agree to do
> this:
>
>
> Commit only to trunk: Mark with 0.98
> Commit to 0.95 and trunk : Mark with 0.98, and 0.95.x
> Commit to 0.94.x and 0.95, and trunk: Mark with 0.98, 0.95.x, and 0.94.x
>
> Commit to 89-fb: Mark with 89-fb.
> Commit site fixes: no version
>
> Should we remove 0.96 tag for now until the branch appears again?
>
> Thanks,
> Jon.
>
> On Thu, Apr 4, 2013 at 10:10 AM, lars hofhansl <larsh@apache.org> wrote:
>
> Thank Jon,
> >
> >I do not think we have to include anticipated future branches in the tags.
> >The release notes are not accumulative but list changes made for each
> release.
> >
> >So if something is in 0.95.x a 0.96 tag neither needed nor wanted (IMHO)
> until we actually have a *parallel* 0.96 branch.
> >
> >That is why all 0.95+trunk changes *have* to be tagged with 0.98 as well,
> because at this point the two branches are in parallel. Actually we should
> go through and make that so in jira.
> >
> >That means the 0.96 tag is not needed right now (and in fact will make
> just confusing, because at the time we do release 0.96 we'll see the same
> issue in the release notes twice)
> >
> >-- Lars
> >
> >
> >
> >________________________________
> > From: Jonathan Hsieh <jon@cloudera.com>
> >To: dev@hbase.apache.org
> >Sent: Thursday, April 4, 2013 8:40 AM
> >Subject: Marking fix version
> >
> >
> >Hey all,
> >
> >I just wanted to make sure we are on the same page here when we committing
> >code and that we are consistent when marking fix version in the jira.  Its
> >pretty important that we get this right because our release notes are
> >generated from these as of 0.94.
> >
> >Here's what I'm doing and suggesting
> >
> >Commit only to trunk: Mark with 0.98
> >Commit to 0.95 and trunk : Mark with 0.98, 0.96, and 0.95.x
> >Commit to 0.94.x and 0.95, and trunk: Mark with 0.98, 0.96, 0.95.x, and
> >0.94.x
> >Commit to 89-fb: Mark with 89-fb.
> >Commit site fixes: no version
> >
> >My understanding is that 0.96 will be a branch off of 0.95 -- so any fix
> to
> >0.95 is a fix to 0.96 until 0.96 branches.
> >
> >Thanks,
> >Jon.
> >
> >--
> >// Jonathan Hsieh (shay)
> >// Software Engineer, Cloudera
> >// jon@cloudera.com
>
>
> --
> // Jonathan Hsieh (shay)
> // Software Engineer, Cloudera
>
> // jon@cloudera.com
>

--bcaec51ddd49798c6904d98d86cf--