[Kolab-devel] KEP #11: Development and Release process outline

Christoph Wickert wickert at kolabsys.com
Wed Aug 31 16:39:55 CEST 2011

On Thursday 25 August 2011 11:33:54 Jeroen van Meeuwen (Kolab Systems) wrote:
> Hello there,
> I've attempted to sensibly outline a development and release process for
> future development for and releases of Kolab;
>   http://wiki.kolab.org/User:Kanarip/Draft:Development_and_Release_Process

Hi Jeroen,

thanks for taking the time to write this very detailed and well thought out 
KEP. The KEP is based on discussions we had internally, and I am very happy 
you have taken my ideas into account. But still there is a tiny detail I am 
not sure about: Should we really release on a Monday?

IIRC we had some bad experiences in Fedora with Mondays and therefor switched 
to Tuesdays. Historically we often released Kolab on Fridays. This gives 
interested people time to play with it over the weekend and we have the first 
bug reports already the next Monday. This enables us to catch issues before 
sysadmins upgrade their productive environments.

Other than that the KEP is fine and gets +1 from my side. More suggestions and 
comments anybody?


Christoph Wickert
Senior Engineer

Kolab Systems AG
Zürich, Switzerland

e: wickert at kolabsys.com
t: +49 251 871 369 77
w: http://kolabsys.com

pgp: 85DACC63 Christoph Wickert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110831/e9dc36d5/attachment.sig>

More information about the devel mailing list