This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: 4.2 Backport fix for PR libfortran/31196
On Mon, 16 Apr 2007, Steve Kargl wrote:
> This is the proposed development model
>
> |
> +-- GCC 4.2 branch created -- (20 Oct 06) ----+
> | |
> Mainline Frozen (20 Oct 06) |
> | v
> | GCC 4.2.0 release (4 Nov 06)
Without relaxing the quality standard for releases to essentially that
applied for branching (100 P1/P2 regressions), this is hopelessly
unrealistic.
To release a week after branching, you must branch at a point that is
release ready. Thus, we'd have ended up branching around now, with
mainline in release branch mode for six more months.
With such relaxation, just release immediately after branching; no
mainline freeze needed.
> This model can work if all the cats can be herded for 1 or 2 weeks.
Volunteer effort is not redirectable that way, although the fallacy that
it is is not original to GCC. Freezing mainline will lose the effort that
would have been directed there, or maybe direct some of it to the same
work but on development branches; the proportion redirected to release
branch work will be negligible.
--
Joseph S. Myers
joseph@codesourcery.com