[geeklog-devel] Geeklog 1.6.2
dirk at haun-online.de
Sat Dec 5 16:59:48 EST 2009
>What is the proposed timeline for releasing Geeklog 1.6.2?
I haven't given it too much thought yet, actually. Certainly not before
February, I'd say.
Maybe this would be a good opportunity to talk about a fixed release
schedule again? While I'm with Dries on detailed roadmaps, a fixed
released schedule does have its advantages: It would make it clear until
when a feature has to be completed to make it into the next release and
would avoid discussions about squeezing in things at the last minute.
What would be a good schedule? A release every 6 months, maybe? 3 months
is probably too short. Mercurial chose a 4-month cycle, for example.
Assuming a 6-month cycle and taking GSoC into account (insert standard
disclaimers about acceptance here), this could be April and October. Do
we want to pin it down further (like April 1st or "first weekend in April")?
A feature freeze would happen, say, 4 weeks before the scheduled release
date and would be followed by a beta and release candidates.
After a release, we could allow for a short window (4-6 weeks or so) for
a bugfix release, if necessary. After that, any further fixes would have
to wait for the next release. Security fixes would still be rolled out
ASAP, as usual.
 "Screw Roadmaps" - Dries Buytaert
More information about the geeklog-devel