Brian E. Fox wrote:
I have been saying that the trunk is too changed for 2.1 for a while also. I think having it as 3.0 is probably the logical thing to do and then we can really buckle 2.0 down as it should be and start making these bigger destabilizing fixes/small features to a 2.1 branch cut from 2.0.10. Unless 2.0.10 gets worked out real soon, perhaps we even go back to 2.0.9 and branch there (ie 2.0.10 becomes 2.1.0)
I agree. Ideally there should be no backward-incompatible or significant changes between 2.0.x and 2.0.y. New features - not necessarily major but would require migration of sorts - should go in 2.z releases and yes 3.0 is probably best for very significant refactors, as is trunk ATM.
I think users have a hard time understanding why a build worked in a previous 2.0.x release but not in the latest.
Cheers --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
