Release timing

Vlad Dascalu vladd at
Thu Jan 13 10:14:41 UTC 2005

Gervase Markham wrote:

> - Has it been around six months since our last release? No :-)

We never said that releases should be 6 months apart. We only talked 
about freezes.

We could modify the plan and say that freezes happen 6 months after the 
last release is out. So the time distance between releases would be 6 
months + the time required for stabilization. This would still allow 
time-based releases, but would prevent situations like this one. Just 


> The only reason I can see to release 2.20 soon is because now is about 
> the time we said we'd release it when we did the initial plan a year 
> ago. There's a much-parodied but useful saying in my company: "A plan 
> is a basis for change". So much has changed in the circumstances; is 
> now not time to change the plan?
> If we are really planning to support every release for 18 months, 
> having releases closer than 6 months apart would be horrible. I 
> suggest that option c) is correct.
> We should unfreeze the trunk, check in all those patches which are 
> waiting, and refreeze about four months after the date we release 
> 2.18, aiming to release 2.20 six months after that date.
> Gerv
> -
> To view or change your list settings, click here:
> <>

More information about the developers mailing list