Sumbry][ wrote:
I'm relatively new to dbmail development, and have been lurking for quite a while and quietly following the latest CVS. Honestly, I do not believe dbmail 2 should even be in RC phase.
<snip> > I honestly suggest reseting the RC numbering, implementing most of the > changes that were talked about, and then starting the RC process over > again.
Absolutely agree. I've been a longtime lurker as well, and am running 1.2.6 in production awaiting a stable 2.0 release. I would far prefer to see all the invasive changes introduced with the 2.0 release rather than having to migrate again to 2.1 or 3.0.
It seems to me that the only reason there is strong objection to major changes to the 2.0 tree at the moment is because it has 'rc' in the revision number. Why can't we just admit that it's not ready for "release candidate" status just yet, make the changes we _need_ for a stable and long-lived 2.x series and then go RC when it's finally ready?
Simon. -- Simon Cocking <[EMAIL PROTECTED]> Network Operations -- MailGuard Pty. Limited Melbourne 68-72 York St South Melbourne VIC 3205 P +61 3 9694 4444 Sydney Level 39, 2 Park Street Sydney NSW 2000 P +61 2 9004 7889 Message protected by MailGuard: e-mail anti-virus, anti-spam and content filtering. http://www.mailguard.com.au/mg
