autocreate/autosieve targeted for 2.5-next

Jeroen van Meeuwen (Kolab Systems) vanmeeuwen at
Thu Nov 18 18:11:37 EST 2010

Hi there,

I just wanted to let you know autocreate/autosieve integration[1] has been 
retargeted from milestone "Future" to milestone "2.5-next".

Traditionally, we fix everything in the master GIT branch first, and we could 
later have a look at backporting the autocreate/autosieve to 2.4.x.

We will most likely *not* ship autocreate/autosieve as part of any 2.4.x 
release, as this stable branch has barely recovered from the huge changes in 
comparison to the 2.3 series. Since it is mainly Murder enhancements failing 
now, we want to enable large shops to move to a stable 2.4 series release 
before touching anything in there in a non-bugfix fasion.

The issues we're looking to resolve before a next bug-fix release is issued in 
the 2.4 series, are listed here:

The feature enhancements and tasks targeted to be resolved for '2.5-next' as 
we call it, are listed here:

This includes we'll fire off snapshot releases directly from the master branch 
at random or regular intervals, and we hope you will enjoy testing!

Kind regards,

Jeroen van Meeuwen


Senior Engineer, Kolab Systems AG

e: vanmeeuwen at
t: +316 42 801 403

pgp: 9342 BF08
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the Cyrus-devel mailing list