On 11 Aug 2010, at 15:13, Zeev Suraski wrote: > Maybe I'm old school, but in my opinion, trunk should only contain > agreed-upon features. It should also always build and pass tests > successfully. It's not the wild-west version of PHP, it's PHP's next > version, in progress. Want to work on something experimental or > controversial? Do that in a branch, merge it if & when it gets accepted to > the language.
I think that depends upon (a) consistency with how it was done last time; and (b) what you're used to. I've worked on plenty of projects where the trunk was bleeding edges and branches are used for release preparation. Melanie -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
