Fred Oliver wrote:
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.)
Indeed there is value in collapsing them especially if we no longer
support that version, but for me it is a bit too soon to merge them all
at this stage in the life of River. Maybe we also have to go through all
the issues and see what is still relevant in the context of River.
JIRA supports merging versions (collapsing) so we can do it at a later
date, we are getting good at making decisions at a later data ;-)
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 very valid point. Still I think there is some value in having a custom
field. I agree that when the moment is there we should be able to get
rid of it and JIRA supports disabling a field so it no longer shows up
in the issue screens but still remains a field you can perform queries
over (don't know for sure though). Eventually we can also remove the
field but then data will be lost forever (this one I know for sure).
So I'll create the custom field, but we can still decide whether we also
want to include the link to the public view on Bugtraq in the
description as I showed in my previous email. It ain't that much work
and when we disable the Bugtraq field we still have the link in the
description.
A placeholder token of "AR1" for the next release is also reasonable.
I'm fine with a placeholder of AR1 with a description to the version
number that it is a temporary version number to be changed for final
release (this description will show up at various places in JIRA such as
roadmap, release notes, etc.).
--
Mark
