Parent POM major.minor version convention, 1 vs 1.0 ?

[Cantor, Scott]

On 9/18/13 4:05 AM, "Ian Young" <ian at iay.org.uk> wrote:
>
>> 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.
>
>Not wanting to go off in a different direction, but I think it might be
>clearer to tag the release the same as the version in JIRA, i.e., 3.1.0.

I'd really be in favor if just putting "1.0" into Jira, with the parent-v2
prefix used to handle the specific exception of the V2 stream. Eventually
that becomes more or less ignored.

>  Having these things correspond would also have the advantage that the
>major version number in the tag would have the usual meaning under
>semantic versioning (it would always be "3" for the V3 parent because
>anything which would change the major version of the V3 parent would be a
>case where we'd want to create a V4 parent).

Where I was headed was avoiding this notion of a "Vx" label since we have
no specific product to tie the label to, if we have the IdP on X and the
MDA on Y, etc. It felt arbitrary. Whereas just starting from major version
1 now and increasing as needed (if we can decide what "need" means) seems
less arbitrary. And of course it doesn't have to start at 1, we could
start at 3 and do 3.0.

-- Scott