[Dovecot] Dovecot v2.0 hg tree
http://hg.dovecot.org/dovecot-2.0/
I just did the initial commit for master process rewrite, which marks the beginning of Dovecot v2.0. Several things are still missing/broken, but at least I was just able to successfully log in using imap :)
I left v1.3 hg tree there for now, but once v2.0 tree is fully usable I'll just delete the v1.3 tree.
Note the new dovecot-master-example.conf, which you'll need to !include to get the services running. Some settings have also been removed because they're now more generically set in the dovecot-master.conf. I'm thinking that perhaps the config process could still be run in compatibility mode where it's able to use an existing v1.x dovecot.conf and translate the old settings to new settings.
On Apr 23, 2009, at 8:04 PM, Timo Sirainen wrote:
http://hg.dovecot.org/dovecot-2.0/
I just did the initial commit for master process rewrite, which marks the beginning of Dovecot v2.0. Several things are still missing/ broken, but at least I was just able to successfully log in using imap :)
I left v1.3 hg tree there for now, but once v2.0 tree is fully usable I'll just delete the v1.3 tree.
Timo, Is there any reason to follow the 1.3 tree?
Thanks, Jonathan
On Fri, Apr 24, 2009 at 3:04 AM, Timo Sirainen tss@iki.fi wrote:
http://hg.dovecot.org/dovecot-2.0/
I just did the initial commit for master process rewrite, which marks the beginning of Dovecot v2.0. Several things are still missing/broken, but at least I was just able to successfully log in using imap :)
How do I retrieve a copy for testing? Can I do "svn co ..." ?
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223
"Clothes make the man. Naked people have little or no influence on society." -- Mark Twain
On Fri, 24 Apr 2009, Odhiambo ????? wrote:
On Fri, Apr 24, 2009 at 3:04 AM, Timo Sirainen tss@iki.fi wrote:
How do I retrieve a copy for testing? Can I do "svn co ..." ?
http://www.dovecot.org/download.html Search for Mercurial Repo
I'll break down and ask the stupid question... Does this mean there will not be a V1.3 release?
I'm currently at 1.1.8 and using mbox. Any comments about the advisability of going to 1.1.14? Better for going to v1.2? What does the crystal ball show for 1.2.0?
As always thanks for all the wizardry....
Timo Sirainen wrote:
http://hg.dovecot.org/dovecot-2.0/
I just did the initial commit for master process rewrite, which marks the beginning of Dovecot v2.0. Several things are still missing/broken, but at least I was just able to successfully log in using imap :)
I left v1.3 hg tree there for now, but once v2.0 tree is fully usable I'll just delete the v1.3 tree.
Note the new dovecot-master-example.conf, which you'll need to !include to get the services running. Some settings have also been removed because they're now more generically set in the dovecot-master.conf. I'm thinking that perhaps the config process could still be run in compatibility mode where it's able to use an existing v1.x dovecot.conf and translate the old settings to new settings.
-- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean@bard.edu voice: 845-758-7475, fax: 845-758-7035
On Wed, 2009-04-29 at 14:01 -0400, Stewart Dean wrote:
I'll break down and ask the stupid question... Does this mean there will not be a V1.3 release?
Yes. v2.0 will come after v1.2.
I'm currently at 1.1.8 and using mbox. Any comments about the advisability of going to 1.1.14?
Better than 1.1.8 :)
Better for going to v1.2? What does the crystal ball show for 1.2.0?
I've been a bit busy developing v2.0 recently and haven't been reading all that much of this mailing list. Once I've done with all the bug reports I'll release v1.2.rc4 and hopefully there won't be many left after that.
Although I don't think the new features have had all that many bug reports anymore recently, maybe I should just set some date to v1.2.0 release. Like maybe "sometimes in May".
participants (5)
-
Jonathan Siegle
-
jsiegle@psu.edu
-
Odhiambo ワシントン
-
Stewart Dean
-
Timo Sirainen