Adopting the Linux/Firefox/Chrome release strategy

[Boudewijn Rempt]

On Thu, 14 Jul 2016, Friedrich W. H. Kossebau wrote:

> Sounds good to me as by-stander.
> 
> Just one thing I wonder: what about fix-up releases with little or big fixes 
> to new features or regressions, which are only uncovered after the release, 
> once the big user crowds have done the real world mass testing? Delaying those 
> 6 weeks as well, until the next release, might be working against an idea of 
> getting things out quickly to the users.
> 
> Thus I propose to consider adding a small time-window after the big release, 
> say 1 week, at the end of which there would be a fix-up release (perhaps only 
> if needed), and only then open the merge window.
> 

If a fix is really, really, really urgent, we can do that, and do a 3.0.1.1, for
instance. But if we'd want to have a week between release and merge window,
then that would cut the stabilization/translation phase back to 3 weeks -- and
we'd be doing something wrong if there would be a fix suddenly necessary after
the four weeks of testing.

After all, after the merge windows close, we'd make dev builds for all OS'es
that people can test.

-- 
Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org