[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=13254728#comment-13254728 ] 

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

I grok the reason about the idea for using sprint numbers in the jira fix version but it raises two questions for me:

1) historically we used to be pretty strict about not having "meaningless" jira versions - that the jira version meant something and it was the actual version used in the release/project metadata.
     does this proposal of having 4.4.1.S116 mean that the version in our pom's/osgi manifest etc. will actually state 4.4.1.S116 or still using "proper" version names/numbers ?

2) I assume if there in one sprint will be worked on two different versions, i.e. devstudio 9.1.x and devstudio 10.x the versions would be something like 9.1.1.S116 and 10.1.0.S116 ? 

...my guess is that the answer to #1 is no and #2 is yes.

And that just make me think ...why put the sprint number into the fixversion ? what is the point ?

Is it because jiralint and our past approach been that we need to set the jira fixversion when working on an issue ? 

Could it then help if we make jiralint or something similar go and set the 'expected fix version' on issues that is in a sprint but have no fix version ? 
In that case dev's won't have to both set the sprint and fix version (unless there is something unexpected about it)



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