[jbosstools-issues] [JBoss JIRA] (JBIDE-22619) Decide strategy for fixversion targets in JIRA

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13257650#comment-13257650 ] 

Nick Boldt commented on JBIDE-22619:
------------------------------------

Note that using M* means that a user who has a M* version installed will have to uninstall to update to GA or Final, because OSGI rules say M > G > F. 

We could consider two alternative approaches:
a) use AM, DM, EM for "A milestone", "development milestone" or "engineering milestone" instead of just M
b) use lowercase qualifiers "final" and "ga", because in OSGi rules (ASCII table), uppercase is less than lowercase, so M < f < g



> 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)