It differs in several ways. a) not assigning a target could mean it was overlooked. Assigning it to backlog means someone thought about it and decided it was for the "future".
b) because we can have various backlogs (say, one for each major facility - like the SDK, uima-as, uimaFIT, Ruta), you can use this to categorize things. A valid objection might be made to this, since you can already categorize things by "component", so maybe only one backlog is really needed. So, I think it's (a) that's the main reason. When you go thru and are about to make a release, it's helpful to distinguish the two states described in (a). -Marshall On 12/17/2014 3:33 PM, Richard Eckart de Castilho wrote: > On 17.12.2014, at 19:55, Marshall Schor <[email protected]> wrote: > >> For the core sdk, following the naming convention e.g. 2.7.0SDK, I named this >> backlogSDK. It is a version we can assign to things that currently have no >> version, but are items for a particular (sub) project where we want to keep >> them >> in Jira to remember to maybe work on them in the future. > How is it different from not assigning a target version at all? > > Cheers, > > -- Richard >
