Leif Jackson wrote:
All,
I am wondering if it might be a very good idea for migrations sake if we
could put the prefix patch into RC8 before release as I believe this will
help more people move off of 1.2 because it will allow them to use their
current setups without re-doing their management systems e.g. changing
code that adds users ...etc. Then if people wish they can rename their
tables but they don't have to. I think it just makes sense plus it
doesn't contain anything that could cause any new bugs that I can see.
What do you guys think?
2.0 is frozen solid. Bugfixes only (so unless you want to file a bug against the dbmail_ prefix...). And about
time we ship that product. I don't see anything major at the moment holding up 2.0.0-final.
As much as I like the prefix patch, it came too late for 2.0.0. I'd rather focus on getting as much features
as possible into 2.1. Then branch 2.1 asap, and continue working on 3.0.
My vision for 3.0: multi-master replication safe, modular sql backend, high-performance imap implementation
with starttls capability (rfc3501), full ldap support. I'd also like distributed storage (delegate different
users to different db-storage servers/clusters), but that may have to wait a little longer :-)
Btw, Ilja -- I kind of miss the wiki. hint, hint.
Leif, I see your point, but I feel that migration from 1.2 to 2.0 will be and remain non-trivial for all
users. In fact, so much so, that I feel that dbmail-smtp/imapd/pop3d actually should refuse to run at all
against a database in 1.2 state. The fact that they do run are cause for serious concern from my point of view
as debian maintainer.
--
________________________________________________________________
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlands________________________________http://www.nfg.nl
