Details
-
Task
-
Resolution: Done
-
Major
-
4.4.1.AM1
-
None
-
devex #116 June 2016
-
https://github.com/jbosstools/jbosstools-build/commit/d0db3e076b2b55cf2bce3b5713c681ea31704076, https://github.com/jbdevstudio/jbdevstudio-product/commit/31b9ba9453a90597178777616cfe26157b891773, https://github.com/jbosstools/jbosstools-download.jboss.org/commit/d88f45a5cd0ffd2a099d1677a2195b0c7c30c587
Description
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?
