Dave Jones wrote:
On Sun, Apr 29, 2007 at 06:36:32PM +0200, dragoran wrote:
> 126.96.36.199 is out ... so whats the plan now? Relase a FC6
> update(updates-testing) or stick with 2.6.20.x until 2.6.22 is
> out/2.6.21 get some more testing?
We could do a rebase to .21 this week, and push that out to testing,
and if anything critical turns up before that becomes deemed stable,
we could push a branched build off of .20 directly to updates.
Most of the scary stuff (new libata pata drivers etc), we'd keep
so things shouldn't be too bad. The timer changes for tickless are
probably the only remaining scary thing. For that we have a few choices.
- Leave NO_HZ off.
Feature parity with FC6, though the code has still changed, and
may still find regressions. Probably the safest option.
- Turn NO_HZ on.
Early preview of F7 features, saves power yadayada, may find new
bugs. (Gets us that nice fuzzy 'f6 bugs are f7 bugs' bonus though)
what kind of bugs would this trigger? crashes? or "only" some weird
if this is done does this also mean that we can backport x86_64 tickless
for F7 when its ready?