I've added 10.2.1.7 to JIRA. It makes sense to have it now because that's the version that sysinfo reports.
However, I don't think it makes sense to track snapshots past a release boundary. Problems should be reported against either latest versions, or official releases. It has been useful in the past to compare snapshots so I think tracking snapshots between releases has some merit. Currently, there are some versions from old snapshot versions hanging around in JIRA. They currently don't appear because they have been 'archived'. However, because they're still around, they appear as the value for the Fix In and Affects fields in JIRA, but you cannot search on them. This is a bad thing, as some bugs are now unreachable in JIRA queries because you cannot specify the correct value for the version in their Fix In. So, I think the plan going forward should be to merge the snapshot versions up to the release version once the release has occurred. I'll update the snapshot-and-release instructions to reflect this. andrew On 10/6/06, Rick Hillegas <[EMAIL PROTECTED]> wrote:
I would mark them for 10.2.2.0. I think that that will be the next bugfix release cut off the 10.2 branch. I suspect what you need to record is: 1) What release did the bug appear in? That would be 10.2.1.6 or earlier. 2) What release will the bug be fixed in? That would be 10.2.2.0 or later. I will probably cut a 10.2.1.7 snapshot sometime soon to catch up with the removal of EoD. However, to date, we don't seem to have marked our snapshot labels in JIRA. Maybe we should. I'm happy not to see the clutter left behind by 10.2.1.0 - 10.2.1.5.
