Ok, for starters I've moved all the open issues from 2.0.11 to 2.2.1
and am now going through them to cull them down where possible.
I've also confirmed that the ITs pass for 2.0.11-SNAPSHOT as it is.
Once I get the 2.1.x bits cleaned up (per original mail that everyone
seems in favour of), I'll spin an RC and see what everyone thinks.
- Brett
On 02/07/2009, at 1:46 AM, John Casey wrote:
+1
Paul Benedict wrote:
My preference is to release 2.0.11 as it is now (37 issues fixed).
The
remaining issues should move to 2.2.1. If critical bugs remain in
2.0.x, then build build a 2.0.12 issue list as people require it.
- Paul
On Wed, Jul 1, 2009 at 10:33 AM, Jörg
Schaible<joerg.schai...@gmx.de> wrote:
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.
The point is, in 6 months nobody knows axaclty anymore what is in
2.0.11-SNAPSHOT. That will actually stop any bugfix release ever.
- Jörg
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
