Simon Cocking wrote:
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.
--
Ilja Booij
IC&S B.V.
Stadhouderslaan 57
3583 JD Utrecht
www.ic-s.nl
T algemeen: 030 6355730
T direct: 030 6355739
F: 030 6355731
E: [EMAIL PROTECTED]
