On 4/22/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > something like a maintainance release for core ?
I don't think there's anything we do to the core at this point that isn't a bug fix. However, there's always the possibility that we've introduced problems in shared, so working from the branch for bug fixes makes sense. My preference would be to release 1.1.2.1 with the bug fix on the branch rather than 1.1.3. My thinking is that bug fixes are minor enough that we can quickly do a minor release without tck testing. When we do get around to doing the testing, we can either release a new minor release (if there was a problem) or post-certify the release at that time. I'd suggest our strategy on minor releases would be to tell people "don't upgrade to a minor release unless the bugs fixed address a specific problem you are having". After all, it works for a certain large non-open-source Seattle-based company. :-) I think it's more important to get a bug fix out quickly, and our current release process for a core major release takes weeks. When enough time has passed, or big enough bugs have been fixed, (or someone is bored and nothing else is going on,) then we can do another major core release.
