Re: Re: RFCs should mention all BC breaks (was Re: [PHP-DEV] PHP 7.4 BC break with openssl_random_pseudo_bytes())
| From: | Pierre Joye | Date: | Wed, 25 Sep 2019 01:47:48 +0000 |
| Subject: | Re: Re: RFCs should mention all BC breaks (was Re: [PHP-DEV] PHP 7.4 BC break with openssl_random_pseudo_bytes()) | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-107318@lists.php.net to get a copy of this message | ||
On Tue, Sep 24, 2019, 3:11 PM Christian Schneider <cschneid@cschneid.com>
wrote:
>
> So here is my question: Am I the only one who thinks BC breaks should be
> fully covered in an RFC before voting?
>
If I am not mistaken this is the rule yes. A specific section should exist
to list BC breaks.
Also a BC break is not allowed in minor versions. The question is also
about what is a BC break, f.e is changing error level a BC break? or the
return value on error?
I am in favour of more strict BC rules for minor versions, but this is a
tricky topic.
Best,