Re: Is the "No BC Breaks in Minor Releases" policy enforceable?
| From: | Fleshgrinder | Date: | Sun, 12 Jun 2016 18:43:38 +0000 |
| Subject: | Re: Is the "No BC Breaks in Minor Releases" policy enforceable? | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-93916@lists.php.net to get a copy of this message | ||
On 6/12/2016 8:21 PM, Rowan Collins wrote:
> A policy of "every BC break should be analysed as a cost-benefit
> tradeoff" might perhaps be a better one than we have now; it is not,
> however, what is written in the Release Process RFC.
>
Which would be arbitrarily laid out anyways. Think of the var keyword
deprecation RFC.
It was random, it is random, and it will be random I guess.
--
Richard "Fleshgrinder" Fussenegger
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc
Attachment: [application/pgp-signature] OpenPGP digital signature signature.asc