[arch-dev-public] [idea] Kernel Release Policy
t.powa at gmx.de
Mon Oct 6 13:49:14 EDT 2008
Am Montag 06 Oktober 2008 schrieb James Rayner:
> On Sun, Oct 5, 2008 at 6:09 PM, Jud <jud at judfilm.net> wrote:
> > Hi Devs,
> > <big snip>
> > So my major point is: The only thing I want to really change is while
> > the newer .x kernel is been prepped for released, Arch does not abandon
> > the current .x kernel.
> Whoa, could have said that at the start :p
> The complication is that kernels need to go through testing, and we
> can't test a 2.6.26.y while there's a 2.6.27 in [testing]. So we can
> either ignore our current rule for kernel to go through [testing]
> making an exception for .y releases - or we can leave the same as it
> is now.
> I'm inclined to leave things the same rather than make an exception.
> Many .y releases are pretty minor, or we have them merged already.
normally the new .x kernel stays 2 or 3 weeks in testing before we move in.
Also all modules need to compile before move in can be done.
The perfect kernel was never released, all have issues the question is how
many are affected and how much are they affected.
A bug in sata/ide/scsi has the possibility to be a showstopper,
also a bug in network or filesystems.
If a speaker on someones soundcard isn't working right isn't a showstopper,
this happens with every kernel/alsa release.
As James stated we cannot move in an older kernel to core without signoff.
Archlinux Developer & Package Maintainer (tpowa)
tpowa at archlinux.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part.
More information about the arch-dev-public