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

Hi! > Isn't that just an excuse to creep in breaking changes? We all > understand the goal here and we all are in favor of it. The problem is > that it still is a breaking change. It would be better to elevate the > E_INFO to an E_WARNING and create that PHP-8.0 branch with the actual > error and start planning the 8.0 release. Changing notice to warning is a breaking change too :) And I'm not sure how rushing 8.0 helps anything if you're afraid of breaks - you get useful features later but also bigger breaks. Long term it doesn't matter anyway unless 7.1 is somehow special, which is not. Also, having just two minor versions seems to be a little thin, unless there's a plan to keep maintaining 7.x, in which case the question is - who's going to do that? -- Stas Malyshev smalyshev@gmail.com