db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: could someone add a 10.2.1.5 as options to appropriate jira fields
Date Mon, 25 Sep 2006 14:12:07 GMT
Rick Hillegas <Richard.Hillegas@Sun.COM> writes:

> Knut Anders Hatlen wrote:
>
>>Andrew McIntyre <mcintyre.a@gmail.com> writes:
>>
>>
>>
>>>done - changed 10.2.1.4 to 10.2.1.5.
>>>
>>>
>>
>>Should we also have 10.2.1.6? If we merge patches to 10.2 now, we
>>can't mark them as fixed in 10.2.1.5 since they're not fixed in
>>10.2.1.5. 10.2.2.0 can't be used since the 10.2 branch is still at
>>10.2.1, and we don't know yet whether the fixes will end up in 10.2.1
>>or 10.2.2.
>>
>>
>>
> Hi Knut Anders,
>
> I'm afraid I don't understand the question. As we've cut new
> candidates, Andrew has scrupulously changed JIRA's full name for the
> 10.2.1 release. Most recently the full name changed from 10.2.1.4 to
> 10.2.1.5. If we have to issue a new release candidate, the name will
> change again--from 10.2.1.5 to 10.2.1.6. I don't understand what it
> would mean to have both a 10.2.1.5 and a 10.2.1.6 in JIRA.

Version 10.2.1.5 is the release candidate, but we don't know whether
it will be released. If we commit something into the 10.2 branch now
and mark it as fixed in 10.2.1.5, it is correct iff 10.2.1.5 is not
released and the name is changed to 10.2.1.6 later. If we mark it as
fixed in 10.2.2.0, it is correct iff 10.2.1.5 is released and the next
official release is 10.2.2.X. Therefore, we don't know what's the
correct fixed-in version until we know whether 10.2.1.5 will be
released.

-- 
Knut Anders

Mime
View raw message