> > Ilja Booij <[EMAIL PROTECTED]> said: > > > I don't think we should do this right now. [snip]
> Aaron Stone wrote: > > the people affected by it are those following the bleeding edge > > of rc's and CVS, folks who are more likely to understand the > > usefulness of a change like this. [snip] Matthew T. O'Connor <[email protected]> said: > Release candidates are not supposed to be bleeding edge! I agree with you, and (Ilja better warm up your flamethrower...) I don't think that DBMail was ready for the release candidate phase when it started. My take on it was that Ilja was looking to put the squeeze onto the broken parts of the delivery chain and get me to start making it work consistently. As it turned out, I had a lot of wrong assumptions and Ilja saved the day. Now that we've stablized the core, I feel like we're out of beta, but not quite ready for release because of a number of annoying details that should be worked out before we foist the annoyances upon the unwashed masses. Like inconsistent binary names, bizarre command lines and funky table names. These are all things which are easily fixed, but represent trivial breakages of backwards compatibility. Clearly this isn't something that can be done in a release series, so we can't do it after 2.0, and yet they're annoying enough that I don't think we'll much enjoy supporting them for the duration of the 2.1 development cycle and release schedule, so we have to do it now. I'm weighing long term annoyance for lots of people vs. short term breakage for not so many people. [snip] > ... meaning feature freeze long since passed, all known bugs squashed, > ready for release barring newly exposed problems. We kinda went at this sideways. We froze temporarily so that we could squash bugs, but we really need to have a selective thaw cycle for the annoyances. Big projects do sometimes take changes at this stage, but only moderated through the release manager. That's why I posted my patches to the mailing list for Ilja to review instead of just committing them willy nilly. Aaron --
