Re: Linux plans for the lenny cycle
On Fri, Apr 13, 2007 at 02:20:28PM +0200, maximilian attems wrote:
> On Thu, 12 Apr 2007, Marc 'HE' Brockschmidt wrote:
>
> > The release team is currently working on a schedule for the lenny
> > release cycle. For that, we want to gather some data from the bigger
> > software packaging teams in Debian first.
> >
> > We would like to know which major upstream versions of linux are
> > expected to be released in the next 24 months and how much time you
> > expect them to need to get stable enough for a Debian stable release.
>
> the current release cycle is 2 weeks for new drivers, subsys changes
> and then a stabilization phase from 6-12 weeks. so i takes between
> 2-3 month for each 2.6 release.
>
> > Our current, very rough plans would mean a release in 18 months with some
> > padding in both directions, which would lead to a lenny release around
> > October 2008. We expect to shuffle this a bit around to fit everyone's
> > needs, so please tell us if this date works for you.
>
> currently 2.6.21 is almost out, so that leaves a window of 2.6.26-2.6.30
> 2.6.28 seems like a good goal, but that is hard to tell in advance
> about the quality of each release. 2.6.20 seems much better than 2.6.19
> and 2.6.18 had also much more testing than 2.6.17.
> staying in sync with fedora releases helps in that regard.
>
> the major upstream user visible lenny changes will be the switch
> from the ide drivers to ata. much better wireless device support
> can be expected and upstream integrated paravirtualized solutions
> (kvm, vmi, ..) dynticks will help on the power saving front.
> alsa added together with ALSA System on Chip layer lots of new
> codecs. as bonus for d-i the cmdline size is bigger and dynamic.
> (plus usual new drivers for new hardware). ext4 has support for
> fs > 16TB. new av32 arch. incomplete ps3 support still.
>
> i'm still looking forward to include half way an updated kernel
> in etch for r1 or r2 release.
Also, it would be good if for lenny we made fuller uses of the possibilities
offered by initramfs, especially the way you can concatenate various cpio
archives together to obtain a single ramdisk. This would be inmensely helpful
both for d-i and the non-free firmware issues.
Friendly,
Sven Luther
Reply to: