Re: release update and branching

[Christian Perrier <bubulle@debian.org>]

>  - upload to unstable
>  	Advantage: Easy, sid_d-i images will use them, fully autobuilt.
> 	Disadvantage: Any sarge fixes would have to go through t-p-u,
> 		which does not currently have a full set of autobuilders
> 		and is still not fully functional per the last release-manager
> 		update. 
> 		This could be risky, depending on the changes we still need
> 		to make in sarge

I also think this is the most appropriate solution at this moment. 

We probably need to be quite conservative in our developments in
unstable so that the sarge-targeted fix still remain easy.

About the l10n issues:

-I'd prefer keeping the string freeze in sarge active. I, along with
 seppy, currently act as interface for several translators and handling
 two branches may be a quite complicated thing for some of them.....and
 explaining everything to them may require me some more time we may not
 be able to afford..:-)

-We have an opened question about "prospective" languages in the
 unstable branch. The number of supported languages in sarge is frozen
 to 40+1, however some more languages are here for a long time and
 it's maybe time for having them tested.

 Opening the gates is a quick task : just remove the entries in
 packages/po/PROSPECTIVE in trunk. This will immediately add the
 relevant po files in place and thus unstable udebs will have the
 translations.

 If some of these packages need to be moved to testing, having
 the extra translation will not hurt (except with the size increase).
 Of course, recompiling the sarge version with the needed fix ported
 to it would then be better.

 So, for the new languages in unstable:

   Pro: give a positive sign to translators, allow new translations
        to be tested, give some new development a push (such as
        early developments of the graphical installer)

   Con: immediate size increase for sid_d-i builds, may need some
        additionnal manual handling when fixes have to go from
        unstable to sarge

Seppy's stats pages are ready now for the branches handling (at least
for level1....we need to think more deeply for other levels) so
there's no problem here. l10n-sync is also ready and currently runs on
both branches.


Another minor topic : it seems that we now agree that the next release
                      of d-i will be THE release. How do we name
                      that beast?

                      Debian Installer 1.0
		        (further fixes for sarge become 1.x)

		      Debian Installer Release 1

		      Debian Installer <codename> with a nice codename

		      Debian Installer no-name-yet :-)