I seem to recall Mark Shuttlework saying in an interview (possibly for Linux Format, possibly somewhere else) that he wanted to work with Debian to get fixed release cycles to help the Debian->Ubuntu porting efforts – It looks like he succeeded in planting the idea! I am looking forward to predictable Debian releases.
The most exciting thing I know of being attempted in the next Debian release (Squeeze) is the multiarch support, which should make running 32 bit apps on a 64 bit OS much better (currently some apps can install if you install the ia32-libs package however others need to be installed in a 32 bit chroot because they have too difficult dependencies to resolve). Redhat adopted another approach where 32 bit is more of a default than 64 bit than on Debian (On Debian a 64 bit install has absolutely no 32 bit support other than the ia32-libs package). Most 32 bit stuff seems to work ok on a 64 bit Redhat box but I don’t know how their approach relates to multiarch. The idea with multiarch is to natively support both 32 and 64 bit packages on the same system (I believe by changing the installer to put 32 bit libs in /lib32/, whereas I believe redhat uses /lib64/ for the 64 bit stuff and /lib/ is still 32 bit only).
I am very interested to see how this pans out as I run a 64 bit desktop at work with lots of 32 bit apps (and gave up on my 64 bit install at home because it was too fiddly for the 32 bit proprietary apps I want to use)
A copy of the Debian announcement is below:
The Debian Project http://www.debian.org/
Debian adopts time-based release freezes firstname.lastname@example.org
July 29th, 2009 http://www.debian.org/News/2009/20090729
Debian decides to adopt time-based release freezes
The Debian project has decided to adopt a new policy of time-based
development freezes for future releases, on a two-year cycle. Freezes
will from now on happen in the December of every odd year, which means
that releases will from now on happen sometime in the first half of every
even year. To that effect the next freeze will happen in December 2009,
with a release expected in spring 2010. The project chose December as a
suitable freeze date since spring releases proved successful for the
releases of Debian GNU/Linux 4.0 (codenamed “Etch”) and Debian GNU/Linux
Time-based freezes will allow the Debian Project to blend the
predictability of time based releases with its well established policy of
feature based releases. The new freeze policy will provide better
predictability of releases for users of the Debian distribution, and also
allow Debian developers to do better long-term planning. A two-year
release cycle will give more time for disruptive changes, reducing
inconveniences caused for users. Having predictable freezes should also
reduce overall freeze time.
Since Debian’s last release happened on Feb. 14th 2009, there will only
be approximately a one year period until its next release, Debian
GNU/Linux 6.0 (codenamed “Squeeze”). This will be a one-time exception
to the two-year policy in order to get into the new time schedule. To
accommodate the needs of larger organisations and other users with a long
upgrade process, the Debian project commits to provide the possibility to
skip the upcoming release and do a skip-upgrade straight from Debian
GNU/Linux 5.0 (“Lenny”) to Debian GNU/Linux 7.0 (not yet codenamed).
Although the next freeze is only a short time away, the Debian project
hopes to achieve several prominent goals with it. The most important are
multi-arch support, which will improve the installation of 32 bit
packages on 64 bit machines, and an optimised boot process for better
boot performance and reliability.
The new freeze policy was proposed and agreed during the Debian Project’s
yearly conference, DebConf, which is currently taking place in Caceres,
Spain. The idea was well received among the attending project members.