On Mon, 25 Mar 2019 at 23:04, Stanislav Malyshev <smalys...@gmail.com> wrote: > > In my opinion, deprecation warnings should be used for functionality > that the used needs to remove from the code. That's not what we're doing > here -
That's a good point. Another thing that probably needs consideration is that if/when someone from the Firebird community steps up to maintain the extension, at some point it would probably be appropriate to fork the extension to be named Firebird, rather than ibase, as it appears that Interbase and Firebird have forked and are no longer fully compatible with each other: https://ib-aid.com/en/articles/differences-between-firebird-and-interbase/ > InterBase was created in 1985: it was the first commercial multi-versioning > database. In the end > of 1999, Borland decided to close InterBase development and published its > source codes under > InterBase Public License. This code was copied (it is permitted by the > license), and Firebird > was born – from the version 1.0 Firebird is a production-ready database, > based on > previous decades of InterBase development. > > .... > > Since then, the difference between Firebird and InterBase became bigger. It would be pretty reasonable for a maintainer from the Firebird community to maintain the extension for Firebird compatibility, rather than maintaining it to be Interbase compatible. But having it still be named after Interbase would be quite confusing. The exact details of that can be discussed after the vote, and when someone applies to maintain it. cheers Dan Ack -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
