Re: Freeze Goals -- WAS: September release
I am no developer, just a satisfied enduser.
I liked the concept of partial freezes someone suggested a while back.
Make in your mind the smallest possible number of packages that is
needed for running a very basic Linux box. When these packages have
the features intended and are of allmost release quality you start
the release cycle by freezing them. Continue with new chunks of
packages until everything is covered.
A script could be made that parses the dependencies from the Packages.gz
files and produces an orderd list of packages most used by others. Use
that list as a guidance to what packages is to be frozen. Select chunks
of packages that doesn't depend to much on each other (unless they are
packaged by the same maintainer or group of maintainers with their own
mailinglist) and only on previously frozen packages.
The release managers must of course have had something like this in their
minds when encouraging maintainers to fix bugs in their packages. If not
there wouldn't have been any quality releases.
The tools needed by the 'boot' and 'cd' guys could be froozen early in
this process to take off some of the last minute pressure they have been
Parsing the Packages.gz files are allready done by scripts made by the
'cd' people and might just need some tweaking to do the job.
Complaints about 'outdated software' I have heard concerns Xwindows
applications and with the partial freeze roadmap these kind of
packages would be froozen late in the release cycle and thus not be