Hi Aaron, > > There are much more important things that should be done I think: > > - speedup of dbmail by marking mail headers, using transaction > > - Sieve > > - dynamic preforking > > These changes will be delayed again. > > Prefixes don't improve the functionality of dbmail, these changes will. > > I'd like to see prefixes because I have dbmail, powerdns and my own > > tables in one database, but not now. > > I am going stir crazy working on 2.0 when I really want to be coding those new > features. The Sieve support is my baby, and I miss working on it! But I also
I really want to see that baby grow FAST :-) > know that I'm going to have to live with the 2.0 branch for a long time while > 2.1 is under development. Better make the most of our relationship with 2.0. "Release early, release often". The dynamic preforking patch seems to be working? It's in the Debian packages as far as I know - so it could be applied to 2.0, tested and a new version could be released after 3 (?) weeks. I'm no friend of collecting a huge number of changes and release rarely - I prefer releasing after every single change. [..] > It was meant to be a 4 - 6 month stopgap and changeover solution, but > instead became the 5 year production system. This happens ALL THE TIME. What's the consequence? We delay dbmail and put more features in? The preforking patch is a candidate. That takes a while so you could finish the sieve patch? That takes a while so we could do the header marking. That takes a while ... never ending storing :-) Release early, release often. Thomas -- http://www.tmueller.com for pgp key (95702B3B)
