I agree with Michael! Other opinions?

Oliver

Michael Smith wrote:
Oliver Zeigermann wrote:

Hmmm, this does not seem to be a small fix...

What should we do now?
- Release Slide 2.0 final without the patch?


-1. This looks to be a substantially important fix. Real software certainly could trip over this bug.


- Release Slide 2.0 final with the patch?
- Release Slide 2.0 RC2 with the patch?


I could go with either of those. It's not entirely new functionality (it's well-tested, because it was previously used in GET - this just moves the code (which is fine) and now uses it in PUT (which is a larger change, but not a huge one).

The conservative approach would be to do another release candidate with this fix, but we might want to take the "get 2.0 out already!" approach (since 2.0 is so clearly a major advance over 1.0.x). I'd tend towards the latter there - the sooner we get people away from using 1.0.x the better, and even though this patch looked large, it was mostly moving code, and isn't particularly risky.

Mike


--------------------------------------------------------------------- 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]



Reply via email to