Cyrus 2.4.1

[Jeroen van Meeuwen (Kolab Systems)]

Bron Gondwana wrote:
> > I'd like to see an open, public beta for 2.4.1.  That will encourage
> > testing in a variety of environments by people who are interested in
> > evaluating and reporting back problems.  It will hopefully avoid the
> > issues caused by over eager sysadmins deploying 2.4.1 to production
> > systems with inadequate testing.
> 
> Sounds reasonable - of course the problem is that 2.4.1 is pretty much
> entire regression fixes to 2.4.0, so we don't want to sell it as more
> beta than 2.4.0!
> 

This means we should allow more time for any significant release to be tested 
and settle next time around.

I'm in favor to have (in our current X.Y.Z versioning schema) Z be bumped with 
bug-fixes only. If we keep it to bug-fixes only, this means we can rapidly 
release the fixes to the community.

Feature enhancements would go into 2.5, for which we could build snapshot 
releases at regular intervals (from the master branch), for those that want to 
live closer to the edge. It'd also increase the opportunity for people to 
provide feedback on the "next M.M release", such feedback to be incorporated 
into the documentation, and would maybe (ideally) also stabilize the next M.M 
release faster, to a point where we would not have to issue a M.M.1 bug-fix 
release as soon as we have to now.

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