What is the Go/NoGo gauge for releases?

[Jerry via Digitalmars-d]

Andrew Edwards <ridimz at yahoo.com> writes:

> On 7/13/14, 7:39 PM, Dicebot wrote:
>> On Sunday, 13 July 2014 at 01:49:16 UTC, Nick Sabalausky wrote:
>>>> So I have some questions: What is the magic number that will
>>>> trigger the release? What happens if we never reach that number?
>>>> Do we just continue waiting for it or do we make a decision at
>>>> some point that it's time? If so, how long do we wait? Is there
>>>> one person who makes the decision, or is it decision automatic?
>>>> If there is a person, who is it?
>>>
>>> My understanding (I could be wrong) is the general rule of thumb has
>>> been "No *new* regressions compared to the previous release".
>>
>> Yup, this is the case. And it is more important than conforming to any
>> specific release date.
>
>
> Meaning, we do not release if there is any open regressions with exception of
> issues 12242 and 6329, the only two that existed prior to or at the time of
> the last release. Got it.

At the moment the regression count is relatively small.  If it gets
larger, adopting the GCC approach might make sense.  The policy there is
that they create a release branch when there are no P1 (highest
severity) regressions.  Other regressions can exist if they are deemed
non-critical, but hopefully still fixing them.