Re: What is the Go/NoGo gauge for releases?
Martin Krejcirik via Digitalmars-d Sun, 13 Jul 2014 15:51:07 -0700
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.
- What is the Go/NoGo gauge for releases? Andrew Edwards via Digitalmars-d
- Re: What is the Go/NoGo gauge for ... Nick Sabalausky via Digitalmars-d
- Re: What is the Go/NoGo gauge ... Dicebot via Digitalmars-d
- Re: What is the Go/NoGo ga... Andrew Edwards via Digitalmars-d
- Re: What is the Go/NoGo gauge for ... Brad Roberts via Digitalmars-d
- Re: What is the Go/NoGo gauge for ... Martin Krejcirik via Digitalmars-d
- Re: What is the Go/NoGo gauge for ... Andrew Edwards via Digitalmars-d
- Re: What is the Go/NoGo gauge ... Brad Roberts via Digitalmars-d