Versioning parent projects in JIRA ?

[Cantor, Scott]

On 9/17/13 10:50 AM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>
>To summarize : we would have JPAR, JPAR2, and JPAR3. A JIRA task like
>"bump dependencies" would be "duplicated" to JPAR2 and JPAR3. Versions
>in JPAR2 and JPAR3 would be the same as the version string in the
>respective Maven POMs. Each major version will get its own JPARx
>project in JIRA.

That's a valid point, we'd be stuck creating a new one on every major
version, potentially. Not sure I like that idea.

Could we create JPAR2 to isolate the 2.x version and then alter the V3
parent versioning going forward to include the major and minor?

We *could* also just embed this in the Jira version, and you can assign
multiple affected and fix versions to a bug. I think you implied that
wasn't possible but it is.

But it's kind of hacky, because you have to embed important info in the
version string.

-- Scott