On 17/03/2007, at 1:37 AM, Jason van Zyl wrote:
No matter how bad the existing behaviour, it is consistent once in
place.
It's not consistent at all. It is totally erratic behavior,
completely defective and counter intuitive. All people are forced
to do is is continually override dependencies in child project to
get the right version.
Poor choice of words perhaps, but I wanted to be clear that this is a
behaviour change, not a bugfix. I think we can possibly make an
exception in this case, but we generally shouldn't be doing that in a
point release.
Our users must be able to trust point releases are safe upgrades.
Let's start moving on putting out 2.1 milestone releases instead.
I think this is a mistake and doesn't help our users. We have not
only the ITs (which are still not good enough but ...) Patrick made
an extensive set of tests plus we have users who have been watching
this issue for a year and can attest in the field to this being a
miserable situation. This is a solution to their problem.
Ok, I think I can accept that it's bad that we make people choke down
alpha code to get this. But I think it's bad that we got into that
scenario too, and it's probably time to start mapping out an actual
2.1 release instead of more point releases beyond 2.0.6.
I'll address the issue itself in another mail.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
