The numbering scheme with the prefix sounds reasonable to me as well.
I'm a bit more inclined to collapse all of the Sun versions into a
single value for JIRA, such as "pre-apache". Since prior versions of
Jini are no longer available for download for browsing or diffs, I see
little value in being more explicit. (I discount 1.2.x as not
particularly relevant.)
Since bugtraq IDs should eventually join old Sun version numbers in
obscurity, I would prefer not to create any long-lived field for them.
A placeholder token of "AR1" for the next release is also reasonable.
Fred
Jim Hurley wrote:
On Jul 17, 2007, at 7:59 AM, Jim Hurley wrote:
On Jul 17, 2007, at 4:25 AM, Mark Brouwer wrote:
:
You will also need all or at least some
historical versions in JIRA to assign the version the issue was reported
against.
Ah - good point. I'll put those in as well.
Going through our open bug/rfe list, it looks like we
have issues that were first reported against the
starter kit, versions:
1.0
1.1
1.2
2.0
2.0_001
2.0_002
2.0.1
2.0.2
2.1
I guess the thing to do is enter those in Jira as versions so
as we enter the issues we can fill in the "Affects Version/s" field.
To segment these into more historical versions (versus
what we're going to create in the River project), I thought
it might be better to preface these with "JTSK_" (for example,
JTSK_1.0, JTSK_1.1). Let me know if someone has a better
idea.
thanks -Jim
