[RFC] Releases planning

[Martin Pool]

On 15 October 2010 15:41, Stephen J. Turnbull <stephen at xemacs.org> wrote:

> But for the release process, I think you should stick with what
> clearly *is* working until (a) it's been formalized and documented,
> and (b) a need for change or a strategic opportunity that can be
> addressed by a process change is identified.

I'm glad you think so because that's what I'm proposing too.  We had a
verbal discussion ahead of 2.2.0 where we said we'd go straight from
the last beta to 2.2.0.  That seemed to work well.  So, now we're just
writing that down as the general policy.

Our rate of new bug filing is slowly going up.  I think the main thing
is that we're keeping more on top of the incoming queue, therefore
deduping bugs better, and we're fixing them faster and making it
easier for new contributors to fix things.

I also agree this frees us up to do more enhancement or big-picture
things; there's clearly some common themes around big files etc.  Some
of these are already happening: memory usage is by no means done but
it's got much better.

-- 
Martin