Hi, I would like to ask for a freeze exception to upload 5.3.3 to unstable and be the version shipped in Squeeze.
As it is a new version, the diff is huge and I'm therefore not including it. Having tracked most of the changes between 5.3.2 and 5.3.3 by following the commits upstream I'm confident about the changes. Plenty of bugs and regressions are fixed in .3, some of which are security vulnerabilities. Some work done here at Debian to reduce the number of failed tests is only part of 5.3.3. Needless to say, trying to get all the fixes in .2 for the major issues would represent a lot of work and increase the delta between Debian and upstream beyond a comfortable level. 5.3.3 has been in experimental for a while now, giving an opportunity to test it. There are two "outstanding" issues on .3, however: * A new SAPI is included: php5-fpm. This SAPI has been in development for years and has been widely used. It supersedes the cgi SAPI, the core is the same that can be found at all the other SAPIS. * There's a change that breaks BC, but it is rather unimportant since namespaces were only introduced in 5.3. Accepting 5.3.3 in Squeeze doesn't represent a transition. No change that requires a transition has or will be made. At this point, releasing Squeeze with 5.3.2 would rather represent a regression. The transition I talked about with some of the RT members at DC10 was meant to finally, and correctly, fix the handling of config files when extensions are removed but not purged. #593266, #593541, #594230, #597217, #422173, and all the merged reports document it. A workaround that doesn't require a transition (based on triggers) was suggested by Sean Finney, but I'm probably going to have to let somebody else take over that. Regards, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
