On 27/07/2016 16:57, Michael Dürig wrote:
>
> In a quick chat with Francesco we came up with a couple of ways of
> achieving this. I.e. we want to have a mechanism to differentiate in
> Jira between issues in oak-segment-tar that we want to have fixed once
> Oak 1.6. is out and those that can be deferred:
>
> 1) Use fix version 1.6. This is confusing as 1.6 has no relation to
> oak-segment-tar whatsoever and we risk messing up the release notes
> for Oak 1.6
>
> 2) Introduce a fake version in Jira ("Oak Segment For Oak 1.6"). This
> is a misuse of the version field probably leading to confusion later on.
>
> 3) Use a label. Might work but then labels are soooo overloaded and
> weak. Also it is difficult to spot and align them in a table in Jira.
>
> 4) Resolve as later. But later is usually never...
>
> 5) Use the assignee field: unassigned issues are tackled post Oak 1.6
> all others are planed to be tackled until Oak 1.6.
>
> My preference would be 5).Well the fixVersion field can have multiple values. So I would say that for segment we have 2 or 3 targets for solving issues. 1) stuff that needs to be solved before oak 1.6 2) stuff that needs to be solved for a specific major segment version; let's say 1.0 3) stuff that needs to be solved by the next segment release; ie blockers. I would suggest then - Rename version 1.6 as "Oak 1.6" - Assign such version to segment versions that *have to* be solved and included by 1.6 - create a "Segment 1.0" version and give it to what you think should go in 1.0. IMO Segment 1.0 does not mean Oak 1.6. It may be the same but I see the two very different. Thoughts? Davide
