[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 3.8 -> 4.0 transition plans
|
From: |
Jordi Gutiérrez Hermoso |
|
Subject: |
Re: 3.8 -> 4.0 transition plans |
|
Date: |
Tue, 03 Dec 2013 13:34:54 -0500 |
On Tue, 2013-12-03 at 10:05 -0500, Mike Miller wrote:
> There is still ambiguity about where non-GUI bug fixes should go. In
> the last release cycle, mostly documentation and regression bug
> fixes went on the stable branch for the next point release. In this
> plan, some measure of criticality will determine whether a non-GUI
> bug fix should go on stable, gui-release, or default.
Critical non-GUI fixes found in the stable release go on stable and
get forward-merged into release-gui and default. We know the GUI is
full of bugs, which is the point of the release-gui branch, so all GUI
fixes go into gui-release. Fixes that break API go into default.
Everything else is shades of grey, but I recommend for starters: fixes
that change non-GUI behaviour or API go into default. Simple fixes can
go into gui-release, more complex changes into default. The shades of
grey are deciding what "simple" and "complex" mean, but we can judge
these on a case-by-case basis.
- Jordi G. H.