The road to 4.3

Tom Albers tomalbers at
Sat Jan 3 20:52:01 CET 2009

Op Saturday 03 January 2009 20:14 schreef u:
> it would be great if we could do a beta (or whatever you want to call it) 
> every two weeks to allow for a faster test-fix-test cycle during the 
> stabilization (non-feature-dev) period of the cycle.

Please note that there is a week between tagging and releaseing. I considered reducing the time in my previous mails, but it requires a faster tagging to release period. 

So without changing the week between tag and release it goes like this for a 2 week cycle:
week 1 wednesday: tagging b1
week 2 wednesday: releasing b1
week 3 wednesday: tagging b2
week 4 wednesday: releasing b2

Which effectively means that you have 1 week to get the bugs and fix them, though receiving bugs during week 3 is not that bad, new fixes can not longer be added to b2.

So, to work with a 2 weeks beta cycle, we need to reduce the period between tag and release:
Week 1 monday: tag b1
Week 1 wednesday: release b1
Week 3 wednesday: tag b2
Week 3 friday: release b2

Which effectively means that the period has increased to 2 weeks, which is a lot better imho.


More information about the release-team mailing list