[
https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen edited comment on JBIDE-22619 at 6/28/16 5:56 AM:
----------------------------------------------------------------------
This problem is not unique for M* also applies for S* - but I thought the use of jgit
timestamps included removing the qualifier so I hadn't considered this.
This was btw. *one* of the reasons we moved away from M* to using alpha/beta etc. now that
I remember it
I think B is a nogo - GA and Final is the general recognized way to write it.
In A, DM and EM don't work either if we need to do CR's, so AM1, AM2, ... would
work since its clearly not just an A or Alpha.
was (Author: maxandersen):
This problem is not unique for M* also applies for S* - but I thought the use of jgit
timestamps included removing the qualifier so I hadn't considered this.
This was btw. *one* of the reasons we moved away from M* to using alpha/beta etc. now that
I remember it
I think B is a nogo - GA and Final is the general recognized way to write it.
In A, DM and EM don't work either if we need to do CR's, so AM would work, or just
A1,A2, ....?
Decide strategy for fixversion targets in JIRA
----------------------------------------------
Key: JBIDE-22619
URL:
https://issues.jboss.org/browse/JBIDE-22619
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Affects Versions: 4.4.1.M1
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Fix For: 4.4.1.M1
We need to decide the strategy for milestones / fixversions in JIRA.
One suggestion has been to align fixversions w/ sprint numbers, thus:
* 4.4.1.S116, 4.4.1.S117, 4.4.1.S118, 4.4.1.S119, ...?
instead of
* 4.4.1.Alpha1, 4.4.1.Alpha2, 4.4.1.Alpha3, 4.4.1.Beta1, ... ?
Questions/concerns:
* what do we do for unscheduled milestones (4.5.0.Alpha1, 11.0.0.Alpha1) and placeholders
(4.4.1.Final, 10.0.1.GA) ? Should we just use Alpha1 or Final/GA until we know which
sprint applies?
* whatever schema we adopt has to work with bzira and jiralint
* any other systems that parse JIRA for integration purposes?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)