[
https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22619:
------------------------------------
In build.next call yesterday Alexey decided we should move ahead with using Sprint numbers
in JIRA as fixversions.
As to how this is related to jgit timestamps, we need SOME suffix in foundation.core and
devstudio.central to define the vanity version of JBT and devstudio, so that we can
differentiate milestones / sprint releases in ide-config.properties. Thus we either use
Alpha1, Alpha2, Beta1, etc. or we use Sprint numbers.
Since we're no longer doing quality stages (eg., waterfall is dead, long live agile)
sprint numbers are more useful/representative of what we're actually doing.
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.S116
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Fix For: 4.4.1.S116
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)