Hi Christoph, I'm hoping we could have a transition ticket filed for kfreebsd 10.1 in time for the release team talk at DebConf today (and Cc'd to -boot@). What else do you think we need for this?
I plan to mention: * packaging of 10.1 snapshots began some 3 weeks ago, it is in experimental and got through the NEW queue already * upstream release timeline - currently proceeding on schedule. they're in 'code slush' already and are due to freeze on 5th September * upstream security schedule - by the time of Jessie release, 10.1 will be supported (for a long term), but not 10.0 * we're already using some features that were new/unimplemented in 10.0, such as newcons that Robert backported an early version of, and KMS which should have matured some more in 10.1 * clang-3.3 is being dropped from jessie/sid in favour of clang-3.4 or 3.5: upstream already builds 10.1 with clang-3.4, whereas 10.0 would need some bits backported by us (not too difficult though) * it's working fine with d-i: I've been using 10.1 kernels exclusively while working on the bugs reported in d-i beta 1 The actual 'transition' part will be kfreebsd-kernel-headers from 10.0 to 10.1 (so, hopefully smaller than the 9.2->10.0 transition that happened earlier this year); reverse depends are mostly freebsd-libs, but also libc0.1-dev, and from there it could affect a lot of things, I don't suppose we're expected to rebuild the whole archive? We could do test rebuilds of selected stuff though if advisable; I could easily borrow/rent some hardware to do that if needed. Regards, -- Steven Chamberlain ste...@pyro.eu.org
signature.asc
Description: OpenPGP digital signature
