Aaron Stone wrote:
Matthew T. O'Connor <matthew@zeut.net> said:
Paul J Stevens wrote:
Only clean and well tested fixes. No more butt-ugly hacks just for
performance sake.
Amen my brother! Please let the 2.0 branch not be a moving target!
Accecpt it's limitations and make the improvements in 2.1.
Are there only bugfixes and new features, or is there a middle ground
where we improve and mature the application?
Of course there's always place for improvements apart from bugfixes even in a stable production release. Your
work on the performance of the acl code and _ic_list can fit into this approach very well. But the
configparser and preforking belong to 2.1, imo.
In my experience, there should always a be someplace for non-drastic
changes to go, otherwise you lose the feeling of motion on a project and
everything becomes this nebulous, "Oh, just wait for verion X.Y and we'll
have that feature."
You will *always* have to wait for a future version for added features :-)
Still, point taken. I don't want to discourage you from working on dbmail. Far
from it.
Question remains howfar you are willing to take 2.0.x before you join me on the
2.1 bandwagon...
--
________________________________________________________________
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlands________________________________http://www.nfg.nl