Trygve Laugstøl wrote:
Kenney Westerhof wrote:
+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.

Minor releases can't break APIs, we agreed on that a long time ago. Minor releases can only add functionality.

Ok.


so -0 on bugfix versions in the poms on trunk.

I don't understand why you don't want to keep the mainline work on trunk? When 2.1 is release should we branch it into /branches/2.1.x immediately and leave trunk/ dead for 6 months?

yes and no, we should continue working on 2.2, new features.
2.1.x is maintenance and only has to be used for bugfix releases, which should (in an ideal world) not happen ;)

Also, it was decided that bugfixes should happen on trunk first, then be 
backported
to the branch. (unless that has been reversed?)

It's consistent with maven itself. We have 2.1-snap on trunk now, as we had
2.0-snap before. When 2.0 was released it was moved to a maintanance branch.
This approach is documented on the wiki, and I say we stick to it, even for
other maven top level projects.

-- Kenney


--
Trygve

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



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

Reply via email to