Knut Anders Hatlen wrote:
Rick Hillegas <[EMAIL PROTECTED]> writes:
Knut Anders Hatlen wrote:
Andrew McIntyre <[EMAIL PROTECTED]> 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.
Thanks, Knut Anders. Now I understand the question. Right now I
recommend not checking anything into the 10.2 branch unless you think
it's really important. I would like to stabilize this branch now that
we're cutting release candidates. Once we vet the release, then we can
go back to porting fixes from the trunk to the 10.2 branch.
If you have to check something into the 10.2 branch, then I recommend
the following approach:
1) Mark the JIRA as fixed in 10.2.2.
2) If I have to spin another release candidate, then I will change all
the "fixed in 10.2.2" to "fixed in 10.2.1" and add these JIRAs to the
bug-fix section of the release notes.
Does this sound reasonable?
Thanks for bringing this up.
Regards,
-Rick
