Hi Pierre, Am 08.09.2012 um 20:23 schrieb Pierre Joye <pierre....@gmail.com>: [...] > >> 3.) Upgrades are hard, let’s go shopping aka never change a running system > > What do you mean here?
A general reluctance to change production systems because "they work". But as I said, not our problem. [...] > No chance to achieve that with the current resources. Simply impossible. That depends on what duties the internals developer define for themselves. If it is to run test suites of the top X extensions and document the outcome it totally sounds possible. It could even be part of a continuous integration process. For me it is not so much about more work, but about more transparency (e.g. the memcache extension and 5.4, only thing missing was a PECL release). Again, the proposal, a little more concise: - Find out about top X extensions - Define their compatibility as blocking for a new release (as an adjustment to the release process) - Maintain a status page and the related bugs - Publish the current compatibility status so that people know The alternative to not fixing this problem is an increasing gap between what we think people should use in production and what they actually use and expect us to maintain. Additionally fixing compatibility issues is usually a good starting point for new talent. [...] > About APC, yes, I definitively would like to get an opcode cache only > version of APC, with very few or almost no ini setting, no user cache, > cleaned from all these esoteric ( 0.01% of the users using them), etc. > But that's a different topic :) That’s indeed a different topic but it would ease a lot of pain to have a fully compatible APC from day one. cu, Lars -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
