Versioning parent projects in JIRA ?

[Cantor, Scott]

On 9/17/13 12:16 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:

>The JIRA versions include the existing 1,2,3, and 4 for
>java-parent-project, and I added parent-v2-1, parent-v2-2, and
>parent-v3-1. This matches the filename of the publicly released POM,
>parent-v2-1.pom for example[1]. I will try and figure out what issues
>were fixed in parent-v2-1 and will "release" in JIRA with a date of
>April 10 2013.

I'm ok with leaving the parent-v2 stuff in so we don't waste time copying
issues all over the place, and maybe we can even punt on a JPAR2.

But I really think we should just major.minor the later stuff instead of
putting parent-v3 in the version.

Concretely, I'm suggesting removing dependencies or making an incompatible
change to the POM would be a major version change, and anything else a
minor.

-- Scott