>> we release PHP7 without any big BC break, give people transparent >> performance improvement.. >> >> then we can do minor bc breaks in the second number releases... 7.1 , >> 7.2 > > That is more or less the opposite of the agreed release process - obviously > we can have *minor* bc breaks later, but putting things off from a 7.0 > release to encourage adoption just puts off the problem and risks 7.1 > becoming a repeat of 5.3/5.4 in terms of adoption.
Right - major versions are for major changes. Minor versions are in bc hell. Actually, even the ext/mysql developer folk are not very happy with ext/mysql. Let me quote a mail from 12/2012 Adam Harvey "I ended up leaving the vote open for a couple of extra days (been a busy week), but I've now closed the ext/mysql deprecation vote. The full results are at https://wiki.php.net/rfc/mysql_deprecation — the short version is that the final vote was 25-12 in favour of deprecation in PHP 5.5. This made the second question moot, but for the record, the result there was 26-12 in favour of option (a) (deprecation in PHP 5.6 if not in PHP 5.5)." In the official Oracle mysql courses, we tell people about mysqlnd, mysqli and PDO Mysql. We tell them to get rid of ext/mysql related code - and not just since yesterday. I know this extension also runs (sort of) with mariadb. But so do others. It's time to say goodbye. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: l...@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
signature.asc
Description: OpenPGP digital signature
