Re: What is the Go/NoGo gauge for releases?

[Martin Krejcirik via Digitalmars-d]

What is essential, is to keep fixing bugs _after_ the release, 
i.e. do point releases. It's shame we don't have one for 2.065 
already. Part of the problem is tracking which bugs are actually 
affecting a release branch. Another is a need to backport later 
discovered bugs.
IMHO all regressions affecting release branch (after the .0 
release) should require pull request on release branch.