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<[email protected]> 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: [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]
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: [email protected]
For additional commands, e-mail: [email protected]
