Prepare for the release (bis repetita placent)

[Christian Perrier <bubulle@debian.org>]

> These plans will include a string freeze (which means no change to
> English strings) for all D-I packages. The dates are not well known
> now and I'll let you know as soon as the schedule is finalized.

Now the schedule has been decided by D-I developers at Oldenburg.
The string freeze begins on Sept 30th and will last until Oct 6th.

Release timeline:

        29 Sep last day for udeb changes for tc2
	       udebs propigated to testing (rc1 breaks)
	30 Sep release tc2 (or give up on the idea)
	       string freeze begins
	       start building full CDs for tc2
	 4 Oct full CDs finish building for tc2, are released
	 7 Oct translation uploads
	       last day to upload fixes to packages on initrds
	 8 Oct initrd builds start for rc2
	21 Oct initrd builds finish (or earlier..)
               last day for uploads of any udebs or debs for rc2
	22 Oct udebs propigated to testing (tc1 breaks)
	       full debian freeze probably starts here
	       final CD builds
	23 Oct testing begins 
		- Should we freeze Debian first? YES
	29 Oct web site updates
	       and rc2 release

	Current blocking issues for tc2:
		- 2.6 red screen of dread? (or errata)
		- finish hppa kernel updates
		- integrate pcmcia resource range patch??
			(worries that this may be too hard to test well)
		- powerpc floppy reorg
		- localization-config (needs to get debs to testing)
	And blocking issues for rc2:
		- subversion holdbacks blocking translations uploads
		- top of TODO
		- new ones should always be added to TODO
		- udebs and debs and udeb source must be synced in sarge
	Questions:
		- should tc2 replace udebs in sarge? images in sarge?
		- what to call tc2? Some suggestions --
			pre-rc2
			<release date> "limited deployment"
			rc1.9