The SRM team would like for us to keep s-p-u current with our latest fixes, rather than holding back uploads until just before a point release. This means we may upload multiple candidates before one actually makes it into etch. This should increase our testing base, get us autobuilt on more architectures[1], and hopefully reduce the latency of doing regular point releases.
aba tells me that we should be able to do our first upload real soon now. Once he gives me a go, I'd like to upload a -13. Again, that doesn't mean that -13 will ship in r1 - if we resolve additional issues in time we can always do another upload. Please let me know if you have any concerns about this plan, or if you have any imminent fixes we should wait for. Since both the etch and etch-security branches contain ABI breakers and since neiter of the security issues is critical enough (imo) to warrant an immediate DSA, I plan to merge the security changes into the etch branch and introduce them in r1. [1] kernel-archive.buildserver.net is doing snapshot builds for the etch branch, so that should catch most build issues and help us catch issues in-between uploads to s-p-u -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]