On Thu, Jan 24, 2002 at 09:51:42AM -0800, [EMAIL PROTECTED] wrote: > I think most of the bugs encountered so far in 2.0 have been relatively > minor ones. No branching has yet been done in CVS -- there is only the > "2.0" codeline. Since we never branched before, nobody's yet followed up > on the suggestions to do so with this release. This is probably a good > ifea anyway for a few days/weeks after a major release -- don't yet start > working on new code, just stabilize what's out there. There really was > quite a substantial change from 1.5->2.0, and so it is probably to be > expected that there are some wrinkles as it comes out the door in .0.0 > form. I would expect that probably in the next few days though most of > those wrinkles will be ironed out, mainly if those of us with commit privs > restrain ourselves from adding new features and just go with bug fixing for > a while. Meanwhile we can accumulate feature requests in > http://www.hughes-family.org/bugzilla where by the way you are all > encouraged to report both feature requests and bugs of any severity. >
I agree strongly with branching. This doesn't hinder the development, and it also fixes the bugs, providing a stable release. Perhaps starting next release, we should have three levels of code available, stable (2.0), just released (2.1) and development (2.2 (pre)). (I don't want to fight over the actual version numbers - it doesn't matter to me) After a few days, just released would become stable, and stable be removed. Regardless of how its implemented, I'd like a truly stable package, either by adding the diffs myself, or (perferably) by downloading it. -- Duncan Findlay _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
