Hi! > I would like to see clarity on when fixes have been merged to the RC > branch (git emails are still a bit hard to grok). It would help to > have early communication about fixes you have decided against so we > can argue their merits and so we don't assume you are planning to pick > them up.
So this is the main point I want to change. There will be no fixes "decided for" and "decided against". Once RC1 is out, this is by default the release, and all the fixes since this point go into version X+1. The only exception - and I can't emphasize enough that I want it to be exception, not a usual occurrence - if we have a critical issue in RC1. So by default no fixes are rejected and no fixes are merged - once RC1 is out, fixes are presumed to be in X+1 version. Unless you know this is a critical bug (meaning, there's absolutely no point releasing PHP with it as either one could not use it - e.g. it does not compile - or nobody in his sane mind would use it - e.g. remote security hole) there would be no point deciding or arguing about it. Again, this is a change from what we did before, not a big one, but as you can see it requires some mindset shift. I think it will improve our release process and will make us able to release quick and quality versions. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
