+1, as long as it's done like this:
- use major.minor on trunk
- major.[minor+1] is either api breaking or has new features
- bugfixes should be major.minor.micro, from a maintenance branch for
major.minor.
so -0 on bugfix versions in the poms on trunk.
-- Kenney
Jason van Zyl wrote:
Hi,
The impetus for this is wanting to release the surefire plugin that has
a tiny bug in it. We are versioning our Maven release major.minor.micro
so why don't we do the same with our plugin and treat everything like
we're going to do small incremental releases like we should be doing. I
would like to change all the versions on plugin to follow the
major.minor.micro format starting with the surefire plugin.
Thanks,
Jason.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
