Matthias Pigulla wrote: > I have to back Sebastian with what he said. Obviously the release methodology > currently applied does NOT work, neither for the project nor the community > around it.
It has worked for many years, just because of one problem you don't scrap the process. > BUT: Once you agree the work is done on a branch and you make something > available that has a RC in it's version name, it's GAME OVER. No more > features. Only bugfixes. RCs are there for testing, if you don't test them don't complain when things break. The main reason for RCs is to spot critical bugs and important regressions. Some of those are test suit can pickup, but most issues are discovered through "real" usage. > You cannot expect folks to re-test everything with every new RC, and so it's > not PEAR's fault if they were not the first to notice the problems. That is exactly what's expected. > Remember the discussion about curlies? I also never understood why that had > to be tackled in an RC5. They were removed. Ilia -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
