Re: Guidelines for RFC post feature-freeze
| From: | Derick Rethans | Date: | Wed, 25 Aug 2021 18:09:04 +0000 |
| Subject: | Re: Guidelines for RFC post feature-freeze | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-115826@lists.php.net to get a copy of this message | ||
On 25 August 2021 18:34:18 BST, Nicolas Grekas <nicolas.grekas+php@gmail.com> wrote:
>Le mer. 25 août 2021 à 19:32, Marco Pivetta <ocramius@gmail.com> a écrit :
,
>
>> On Wed, Aug 25, 2021 at 7:30 PM Nicolas Grekas <
>> nicolas.grekas+php@gmail.com> wrote:
>>
>>> I would welcome a new RFC to clarify what is allowed during the feature
>>> freeze.
>>>
>>
>> See
>> https://en.wikipedia.org/wiki/Freeze_(software_engineering)
>>
>
>
>Can you please let me know how that helps?
Maybe you didn't read the post, but generally a feature freeze in software development is some
time were no new features are added so a code base can stabilise. This usually happens just before a
release. These periods are really important as they allow for 3rd party tools, documentation, etc to
be ready when a piece of software is released. On top of that, this period can also be used by users
to make sure everything is stable, and that there are no critical bugs.
cheers
Derick