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

[Jeroen van Meeuwen (Kolab Systems)]

Christoph Wickert wrote:
> 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_Proces
> >   s
> 
> 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.
> 

I have edited the text in Phase 6 to reflect that releasing on a Monday is not 
the idea;

  https://wiki.kolab.org/User:Kanarip/Draft:Development_and_Release_Process#Phase_6:_Final_Release

Please review.

Kind regards,

Jeroen van Meeuwen

-- 
Senior Engineer, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kolab.org/pipermail/devel/attachments/20110905/7782e456/attachment.html>