Zeev Suraski wrote:
Marcus,
For the sake of world peace, let's say you're absolutely right. Let's
be done with this compat mode case study.
The important point is for the future - announce compatibility breaking
changes (removal of features, major changes to features) clearly on
internals@, in a dedicated email inviting discussion. If you get no
feedback - be persistent and ask for even those that support it to move
forward and say so.
Listing it in a shopping list of new features for the next version is
important, but only after such a discussion takes place.
I think such things should be listed and planned on a web page. Be that
the wiki system I put up, or some file on phpweb CVS. It should be a
place where developers (and users) can see what is under discussion,
what is decided and when to expect the change as well links to related
documentation.
That way it is easy for people to get up to speed with things and see
when what decisions were made.
regards,
Lukas
PS: I think the wiki is really showing how useful it is. I have no
problem managing ACL's for the site. However I think it would get used
even more actively if the ACL's would be derived from cvs.php.net .. It
also does not necessarily need to be a wiki, though I think its
convinient for these kinds of documents.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
