Upgrading cyrus

[Jeroen van Meeuwen (Kolab Systems)]

Henrique de Moraes Holschuh wrote:
> On Wed, 22 Sep 2010, Patrick Goetz wrote:
> > On 9/22/2010 4:56 AM, Sven Mueller wrote:
> > > Indeed, upgrading from 2.1.X is probably something we won't support
> > > automatically. I remember this upgrade (to 2.2) being a process that
> > > took quite a bit of hard to automate work. Upgrading from 2.2 to 2.3 on
> > > the other hand actually seems to be mostly a thing of just installing
> > > 2.3 (at least that worked fine on a simple (non-murder) test
> > > installation I did.
> > 
> > Perhaps this means it's time to use a small cloth to polish the HMH
> > branch a bit around the edges and call it a wrap for experimental?
> 
> Feel free.
> 
> Stuff I don't like in the current hmh branch:
> 
> We still have Cyrus utils with bad (generic) names polluting the global
> namespace.  These need to be prefixed with 'cyr', or moved the heck away
> from /usr/bin and /usr/sbin and into /usr/lib/cyrus*
> 
> We still have missing manpages, and some utils are not being shipped in
> any package (which might be a bug, or not).
> 
> We may need to pull whatever is in CVS and still not released, as the
> more active Cyrus developers upstream are focused on 2.4 and other
> stuff.
> 

We are actually using GIT these days; http://git.cyrusimap.org

> I still didn't send the child-fix-related patches upstream.  They fix
> real bugs, but they're not complete yet so they don't fix all bugs.  And
> I didn't update the state machine docs with the stuff the patches
> change.

Can you refer me to these patches? I cannot make any guarantees but I can make 
sure they get the attention they deserve.

Kind regards,

-- 
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +316 42 801 403
w: http://www.kolabsys.com

pgp: 9342 BF08