On Thu, 2005-03-10 at 21:00 +1100, Neil Brown wrote: > On Tuesday March 8, [EMAIL PROTECTED] wrote: > > So here's a first cut at how this 2.6 -stable release process is going > > to work that Chris and I have come up with. Does anyone have any > > problems/issues/questions with this? > > One rule that I thought would make sense, but that I don't see listed > is: > > - must fix a regression > > If some problem was in 2.6.X and is still there in 2.6.X+1, then there > is no great rush to fix it for 2.6.(X+1).1, it can wait for 2.6.(X+2).
this is tricky. I mean, what if it's a datacorruption thing? Sure older kernels may have it too... yet at the same time it'd be nice to get it fixed. And once you go down this slipperly slope you end up with the original ruleset again, eg it must be "somehow relatively important". - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
