Re: Is the "No BC Breaks in Minor Releases" policy enforceable?

On Jun 16, 2016 11:41 AM, "Joe Watkins" <pthreads@pthreads.org> wrote: > > Morning, > > > This would keep the "BC promise" intact instead of going back to > cowboy php days. > > > Please don't let's make it harder to go from 7.0 to 7.1 than it was > from 5.6 to 7.0. > > Can we reduce hyperbole to nil, please. > > Before work starts on PHP 8, we need to have something worth branching, > just as we needed for 7, and 6. > > There is no sense in which the too_few_args vote was unfair, biased, or > anything comparable to "the old days" (it wasn't committed without public > consultation). > > The majority have decided that the *extremely minor* BC break is worth > the tradeoff. We have cases where our view on a problem and its impact was wrong, totally wrong. The rfc process allows veto even if accepted. I am very worried about how things were done here. See my reply to Dmitry's approval mail for the reasons.