<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 28 Nov 2012, at 09:23, Vincent Snijders wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">2012/11/28 <<a href="mailto:michael.vancanneyt@wisa.be">michael.vancanneyt@wisa.be</a>><br><blockquote type="cite">It IS a big change. There is production code out there that uses this,<br></blockquote><blockquote type="cite">and this is an incompatible change.<br></blockquote><br>Then Luiz is right on time with his proposal, with the frist release<br>candidate of the first release that contains this feature.</span></span></blockquote></div><br><div>Personally, I think a release candidate is too late. A release candidate freezes all interfaces (even a beta release does so already, normally). Generally the only fixes still performed afterwards are for blocking crashers/failures, major security holes or build issues. I do believe that maybe this functionality was put in a release too soon after being committed to trunk, given that it changes the interface of the base units and hence the changes are more or less cemented once they are released. But that's a separate issue, which at best can be taken into account in the future.</div><div><br></div><div><br></div><div>Jonas</div></body></html>