+4
Brett Porter wrote:
With the 2.2.0 release coming up, I've started to find the amount of
merging (and consistency of it) is becoming harder, and I think it might
be inevitable that there'll be confusion from users about what release
is the right one to use.
I'd like to suggest the following:
- remove the 2.1.1 version from JIRA and remove the 2.1.x SVN branch -
there seems no point in releasing 2.1.1 if 2.2.0 is out (2.2.1 could be
released for the fixes made that aren't on the RC branch).
- promote the 2.2.0 as the stable release on the site and push all
bugfix work towards 2.2.x
- a 2.0.11 release to get those sticking to 2.0.x the 37 fixes already
committed there.
- declare 2.0.x EOL after that release and delete the branch
Any concerns with this approach?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
