On 07/20/11 - 12:20:43PM, Mark McLoughlin wrote:
On Tue, 2011-07-19 at 14:11 -0400, Hugh Brock wrote:
> Hello all.
>
> With release 0.3.0 about ready to ship it seems like a good time to
> start talking about features we'd like to see for 0.4.0. I'd like to
> continue the three-month release cycle we've been on, so that puts our
> next one around mid-October.
You know, looking at this list, I really wonder - why not release
earlier and oftener?
- we don't have a massive amount of sub-projects; we should be able
to turn around a release very quickly and the more often we do it,
the smoother the process will be
- we're not intentionally breaking anything on a regular basis, so
there shouldn't be any reason not to release more often
- shorter release cycles means the goals for each cycle won't be as
far reaching and hand-wavey, instead it would be a much more
specific set of tasks and features
Why not aim for e.g. every 3 weeks? Or perhaps every 2 weeks?
I've been advocating this for a while. The problem up until this
point has been that doing a release is a large undertaking. There are so
many dependencies, and enough sub-projects, that coordinating them at that
rapid a pace is difficult.
The dependency situation is slowly sorting itself out. We have enough of the
stuff in Fedora, and we are reducing dependencies at a good enough rate, that
this is no longer the huge issue it once was. The sub-components are also
becoming more stable (at least in their interfaces), so I think it would be a
good idea to re-visit doing much more frequent releases.
--
Chris Lalancette