+1 to Nicholas' assessment. Too many firms I've worked with won't be
changing to 2.1/2.2 until it's been in production release for several
months, and probably won't trust it. They'll need critical bug
support on 2.0. We just need a window for migration, that's all.
cheers,
Christian.
On Jun 30, 2009, at 9:52 AM, nicolas de loof wrote:
Brett Porter wrote:
- remove the 2.1.1 version from JIRA and remove the 2.1.x SVN branch -
+1
- promote the 2.2.0 as the stable release on the site and push all
bugfix
work towards 2.2.x
+1
- a 2.0.11 release to get those sticking to 2.0.x the 37 fixes already
committed there.
+1
- declare 2.0.x EOL after that release and delete the branch
non binding -1 : The 2.0 user base is still large, most of them just
don't
yet use the latest 2.0.10. We could just promote 2.2.x as the latest
stable
release BUT still consider a critical bug-fix branch for 2.0.x
2009/6/30 Paul Benedict <pbened...@apache.org>
Personally, I will not be upgrading to Maven 2.2 until the next patch
release. I am skipping 2.1 because there is no 2.1.1. Being
conservative in my approach, I find it just too risky inside an
organization to bring in upgrades without at least one patch release.
Will anyone yet document justification for upgrading to 2.2/2.1 from
2.0? JIRA notes are for the "geeks" but a general summary would be
worthwhile.
I disagree with deleting branches. I think that's extreme.
Paul
On Tue, Jun 30, 2009 at 8:05 AM, Jason van Zyl<jvan...@sonatype.com>
wrote:
On 29-Jun-09, at 7:54 PM, Brian Fox wrote:
Yeah get rid of it. Is there really demand for the fixed in
2.0.11? I
feel like it's EOL now.
I would guess the vast majority of users are still using the 2.0.x
line
because the 2.1.x and 2.2.x lines have come out very quickly and
users
will
probably let those bake awhile. I think there are still too many
inconsistencies between the lines and change between minor versions
happened
a little too quickly for people to absorb. I think the 2.0.x line
will
still
be in widespread use for the next year.
On Mon, Jun 29, 2009 at 7:33 PM, Brett Porter<br...@apache.org>
wrote:
Just a matter of clarity. If its not there, there will be no
question
about
whether to merge to it or not.
- Brett
On 30/06/2009, at 4:12 AM, Paul Benedict wrote:
Hmm...
- declare 2.0.x EOL after that release and delete the branch
What harm is there in keeping it around? Even if you never
return to
it, it doesn't cost you anything to keep it.
Paul
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/SonatypeNexus
http://twitter.com/SonatypeM2E
----------------------------------------------------------
Three may keep a secret if two of them are dead.
-- Benjamin Franklin
---------------------------------------------------------------------
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
Christian Edward Gruber
christianedwardgru...@gmail.com
http://www.geekinasuit.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
