http://dovecot.org/releases/2.2/dovecot-2.2.18.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.18.tar.gz.sig Oops, director was somewhat broken in 2.2.17. I thought I tested the last changes in it well enough, but looks like not. To avoid all existing Dovecot director installations from breaking I decided to make 2.2.18 release quickly afterwards.. BTW. We're planning on making some changes soon to how version control is used in Dovecot development, which should help avoid these kind of problems. The main problem now is that everything gets directly committed to the master branch (although we have a separate more stable dovecot-ee repo also). The new plan is to do something like this: http://nvie.com/posts/a-successful-git-branching-model/ Besides some minor compiling issues and other small changes, the important ones are: - director: Login UNIX sockets were normally detected as doveadm or director ring sockets, causing it to break in existing installations. - sdbox: When copying a mail in alt storage, place the destination to alt storage as well.
On 15.05.2015 13:11, Timo Sirainen wrote:> http://dovecot.org/releases/2.2/dovecot-2.2.18.tar.gz > http://dovecot.org/releases/2.2/dovecot-2.2.18.tar.gz.sig > > Oops, director was somewhat broken in 2.2.17. I thought I tested the > last changes in it well enough, but looks like not.Thanks for being better than qemu and actually releasing a new version rather than just a patch. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20150515/662775a6/attachment.sig>
On 2015-05-15 13:11, Timo Sirainen wrote:> BTW. We're planning on making some changes soon to how version control > is used in Dovecot development, which should help avoid these kind of > problems. The main problem now is that everything gets directly > committed to the master branch (although we have a separate more > stable dovecot-ee repo also). The new plan is to do something like > this: http://nvie.com/posts/a-successful-git-branching-model/GitHub please? :) // Tom