[wwwdocs,committed] Update Stage 4 description

Message ID 8398efbc-6f71-7dd6-680f-c2a94d68f283@suse.de
State New
Headers show
Series
  • [wwwdocs,committed] Update Stage 4 description
Related show

Commit Message

Tom de Vries Jan. 9, 2019, 9:21 a.m.
[ was: Re: [RFC] Update Stage 4 description ]

On 09-01-19 09:47, Richard Biener wrote:
> On Wed, 9 Jan 2019, Tom de Vries wrote:

> 

>> [ To revisit https://gcc.gnu.org/ml/gcc-patches/2018-04/msg00385.html ]

>>

>> The current formulation for the description of Stage 4 here (

>> https://gcc.gnu.org/develop.html ) is:

>> ...

>> During this period, the only (non-documentation) changes that may be

>> made are changes that fix regressions.

>>

>> Other changes may not be done during this period.

>>

>> Note that the same constraints apply to release branches.

>>

>> This period lasts until stage 1 opens for the next release.

>> ...

>>

>> This updated formulation was proposed by Richi (with a request for

>> review of wording):

>> ...

>>  During this period, the only (non-documentation) changes that may

>>  be made are changes that fix regressions.

>>

>> -Other changes may not be done during this period.

>> +Other important bugs like wrong-code, rejects-valid or build issues may

>> +be fixed as well.  All changes during this period should be done with

>> +extra care on not introducing new regressions - fixing bugs at all cost

>> +is not wanted.

>>

>>  Note that the same constraints apply to release branches.

>>

>>  This period lasts until stage 1 opens for the next release.

>> ...

>>

>> If a text can be agreed upon, then I can prepare a patch for wwwdocs.

> 

> The proposed text sounds good, please post a patch and apply!


Attached patch committed.

Thanks,
- Tom

Patch

Index: htdocs/develop.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/develop.html,v
retrieving revision 1.190
diff -r1.190 develop.html
135,138c135,140
< be made are changes that fix regressions.  Other changes may not be
< done during this period.  Note that the same constraints apply
< to release branches.  This period lasts until stage 1 opens for
< the next release.</p>
---
> be made are changes that fix regressions.  Other important bugs
> like wrong-code, rejects-valid or build issues may be fixed as well.
> All changes during this period should be done with extra care on
> not introducing new regressions - fixing bugs at all cost is not
> wanted.  Note that the same constraints apply to release branches.
> This period lasts until stage 1 opens for the next release.</p>