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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-22619:
---------------------------------------------

And I just want to repeat that nothing really changed in what we do about API readyness so lets please not get confused about "we are not doing waterfall" or "we are now doing agile". We never did waterfall, nor are we currently doing GA level agile sprint builds. 

That is a separate issue and IMO much bigger improvement and change to do. 



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