Aaron Stone wrote:
So basically, we'd consolidate all of the ideas in the TODO list for both 2.1 and 2.2 and incorporate the ideas into however many 2.1 releases it takes and then release 2.2 with all of the new stuff stabilized.
Yep. If it's decided that 2.0 is going to be a stable release and 2.1 developmental, then it's pretty easy to get 2.0 out the door now. 2.0 can ship in its current RC shape (assuming there are no showstoppers left in there) and the debate over what should or shouldn't go into the next release can end.
All the proposed features, restructuring, etc. can go into 2.1 and get the testing done there (with a clear understanding that it's a work in progress). Those of us who just want the stable release can sit on 2.0 until 2.2 is ready.
Since dbmail is pretty critical infrastructure for a lot of us, a clearly defined production/developmental release schedule would be hugely beneficial.
-- 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
