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 saint.ack@gmail.com designates
 209.85.161.41 as permitted sender)
MIME-Version: 1.0
Sender: saint.ack@gmail.com
In-Reply-To: 
 <CAAha9a3cfSxQAPay_9_oTqDr17rrDHR_ftZtKbZsp=zuA5qp-w@mail.gmail.com>
References: 
 <CADcMMgHup8aNspXV0=q3jqVgkFP7mqJvEtzjZjB3Fu+_9xtqOA@mail.gmail.com>
	<CAD5C9C1.1FE53%nspiegelberg@fb.com>
	<CADY20s7-qPB3qR6kMdPHhO6J6+4==nKLV6ZY2S=GzLbmM9jBaw@mail.gmail.com>
	<CAAha9a3cfSxQAPay_9_oTqDr17rrDHR_ftZtKbZsp=zuA5qp-w@mail.gmail.com>
Date: Wed, 16 Nov 2011 09:01:09 -0800
Message-ID: 
 <CADcMMgGmc5yUOf2sHh_yWYQ8P0WEjyZF+s_vrWEhAKQMA0DSow@mail.gmail.com>
Subject: Re: Commit Log format
From: Stack <stack@duboce.net>
To: dev@hbase.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Wed, Nov 16, 2011 at 8:18 AM, Jonathan Hsieh <jon@cloudera.com> wrote:
> I've been marching through the CHANGES.txt file for 0.92 -- and have foun=
d
> some bugs in the jira and in the CHANGES.txt file itself (will submit pat=
ch
> to fix these).
>

Thanks boss.

> If we are going to depend on the jira to auto generate, it is becomes
> really important to update fix version on the jira if we are going to use
> the JIRA to autogenerate it! =A0I've been going through an updated the em=
pty
> ones I've noticed.
>

Agreed and thanks for the fixup.


> This brings up another question -- as I've been going I noticed some are
> marked 0.90.5 but also have been committed to the 0.92/trunk branches. =
=A0If
> a patch committed to multiple branches such as trunk/0.90 branches, my
> opinion is that it the fix version include both 0.90.5, 0.92.
> =A0Alternately, we could assume that any 0.90.5+ is in 0.92.
>

My gut reaction is that we mark in JIRA all the versions the fix will
show up in.   0.90.5 is a little awkward since CHANGES.txt has been
kept-up old-style manual edit but I think that when it comes to
0.90.6, 0.94.0, etc., future versions, lets just mark a fix's
inclusion in the one place only (In JIRA).

Good stuff,
St.Ack