current blockers?

[Nathanael Nerode <neroden@twcny.rr.com>]

So if I'm not mistaken, these are the current release blockers
(based on http://lists.debian.org/debian-devel-announce/2005/10/msg00004.html)
There's also a fair amount of testing progression necessary of course.
Have I got this about right?

* releaseable binutils in unstable (necessary for releaseable gcc-4.0)
* releaseable glibc in unstable (likewise)
* 'secondary' g++ transition in unstable (likewise)
* removal of non-free docs from gcc, glibc, binutils (essential toolchain)
* removal of non-free firmware from kernel in unstable
 -- these are all supposed to be done before 30 July 06 so that the
    essential toolchain and kernels can be frozen.  We're not even close
    yet, particularly because it appears that nobody is working on the
    non-free removal stuff.
* mirror split
 -- amd64 inclusion should follow with no trouble
* removal of non-free docs etc. from all packages

This doesn't appear to really be a release blocker, but perhaps should be:
* releaseable freetype in unstable (blocks e.g. openoffice.org)
(also blocks new gcc-4.0 in testing via libcairo!)

This should be solvable by either a reversionary upload or a proper
transition or both.

-- 
Nathanael Nerode  <neroden@twcny.rr.com>

This space intentionally left blank.