Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Date: Tue, 27 Apr 2010 20:19:22 +0200
From: Knut Anders Hatlen <Knut.Hatlen@Sun.COM>
Subject: Re: 10.6 branch and fix versions in JIRA
In-reply-to: <4BD7298E.9060900@oracle.com>
Sender: Knut.Hatlen@Sun.COM
To: derby-dev@db.apache.org
Message-id: <4BD72AAA.5020807@sun.com>
References: <4BD7158C.8030606@sun.com> <4BD7298E.9060900@oracle.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US;
 rv:1.9.1.9) Gecko/20100318
 Thunderbird/3.0.4

On 04/27/10 20:14, Rick Hillegas wrote:
> Knut Anders Hatlen wrote:
>> Hi,
>>
>> There is no 10.6.1.1 fix version in JIRA, it seems. Should we add one so
>> that we can tag fixes that go into the branch after the RC with it? (We
>> should probably bump the version on the branch too. It still says 10.6.1.0.)
>>
>> There is a 10.6.2.0 fix version, though, but I think we agreed that we
>> shouldn't use that version yet, see:
>>
>> http://old.nabble.com/Re%3A-Plans-for-a-10.5.3.1--tt26533770.html#a26577283
>>
>> Thanks,
>>
>>   
> Thanks for bringing up this topic, Knut. I have made the following changes:
> 
> 1) Bumped the id on the 10.6 branch to 10.6.1.1. This number represents 
> the head of the branch.
> 
> 2) Renamed the JIRA 10.6.2.0 release id to be 10.6.1.1 to agree with the 
> head of the branch.
> 
> 3) Added another step to the release instructions, explaining that we 
> expect agreement between the highest JIRA id for a branch and the actual 
> release id at the head of the branch. I added a pointer to the email 
> thread which you located.

Thanks, Rick! I'm able to locate the 10.6.1.1 version tag in JIRA now.

-- 
Knut Anders