[geeklog-devel] Geeklog 1.6.2

Tom websitemaster at cogeco.net
Mon Dec 7 08:51:15 EST 2009

Probably a release every 6 months would be best, than at least the features
that are done can get out the door sooner.

We do need a roadmap for at least the major features proposed.


Then it can at least guide us in a general direction of what new features
will be implemented and when, and possibly by who.

For example, I know we talked about and decided to implement a JavaScript
library and it looks like it may be jQuery?? 

Blaine - you mentioned you hacked the Geeklog core to implement some
JavaScript libraries. Has this code been developed enough that it can be
useful to us?

Other items that need to be added to the Roadmap
- Implementing the Plugin Repository
- "Add Social Networking Features"
- ???


-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun
Sent: December-05-09 5:00 PM
To: geeklog-devel
Subject: Re: [geeklog-devel] Geeklog 1.6.2

Tom wrote:

>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[1] 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[2], 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.


bye, Dirk

[1] "Screw Roadmaps" - Dries Buytaert
[2] <http://mercurial.selenic.com/wiki/TimeBasedReleasePlan>


geeklog-devel mailing list
geeklog-devel at lists.geeklog.net

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4663 (20091205) __________

The message was checked by ESET NOD32 Antivirus.


More information about the geeklog-devel mailing list