Versioning parent projects in JIRA ?

[Tom Zeller]

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

Okay. I like having just one project in JIRA, less overhead.

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

Fine with me. In JIRA it is just a string. Changed to 2.1, 2.2, and
3.1, actually 3.1.0 per below.

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

Okay, if I understand correctly, when I tag and "release"
java-parent-project-v3, the version should be 1.0, corresponding to
version 3.1.0 in JIRA.