Blake Mitchell <[EMAIL PROTECTED]> said: > Maybe I'm missing something obvious here, but why not create a 2.0 > branch, so that HEAD can continue on with whatever new things people > come up with, and not affect the 2.0 release?
I think I'm at fault for some of this. I talked everyone into a "thaw" period to incorporate key breakages that we want to have with us during 2.0. Somehow this was misinterpreted to be an open season for fundamental changes. It is not. So let's be clearer on what's happening: we're in a release engineering phase. Specifically, we are evaluating key changes that break compatibility of previous release candidates, but which provide functionality that we want to have in 2.0. Additionally, I'd appreciate if everyone would try their hand at a full, fresh installation of DBMail. Open up the tarball, look inside, read the README and the INSTALL files. Make sure that it all makes sense. New features should just be completely on hold. I don't think that we're a large enough development group that we can handle a major release engineering and continue to develop new features. Something's gotta give, and it's not going to be the timeliness or quality of the release. Aaron --
