Hi! > - We have an RFC [too_few_args] about to pass that seems to break our > published Release Process. > - Is the vote invalid, or do we need to change the Process? > - The opinions of those who voted "Yes" are particularly requested.
BC is inherently subjective and subject to judgement, since strictly speaking any user-visible change, including bug fixes, can influence outcome of some code, and thus break BC. And some unobviously visible changes could too (e.g. making PHP engine 3 times faster could break someone's security based on certain operation in PHP being slow). Thus, we can state our promise to keep BC as much as we feel is practical, but we should not make a suicide pact of "never change anything, no matter the cost, no matter the circumstance". And the level of acceptability raises from rightmost to leftmost digits, more to the left, more BC break we can accept. But ultimately, I think, it is a case by case basis, with some cases being obvious and some less obvious. For this feature, given how useless and obscure non-passing required parameters is and that it's almost always is a bug, I personally think BC break it acceptable, though I admit it comes pretty close to the line, but on my personal opinion, still does not cross it. Finally, there's nothing "enforceable" in PHP as such - we do not have a legal structure and there's no "force" one part of the community could use on the other to "enforce" anything. It is unusual, different and sometimes frustrating, but I think it worked surprisingly good so far. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
