Re: Stable release state

[David Kastrup]

"Phil Holmes" <address@hidden> writes:

> At present, we're actually premature in proposing a freeze to make
> ready for a release candidate.  We have a number of outstanding
> critical bugs and regressions which need fixing before we go anywhere
> with a new stable release.  So, currently, step one is to reduce them
> to zero.  Step 2 is to propose and agree a development freeze.

Tackling step 1 and step 2 in this order was seminal for 2.16 taking a
year longer than anticipated.

-- 
David Kastrup