Bug#594461: apt-setup: Should propose using t-p-u when testing is installed

[Petter Reinholdtsen <pere@hungry.com>]

[Christian PERRIER]
> After a (short) discussion in -devel, I came up with the proposal of
> activating "testing-proposed-updates" when users install testing, in
> a similar way that we currently propose activating volatile when
> they install stable.

One challenge that should be considered, is what should happen when
testing become stable, and the meaning of testing-proposed-updates
changes.

For example now, testing-proposed-updates is packages intended for
squeeze, and after the release, it will no longer have packages
intended for squeeze.

Should those installing testing today keep using testing, or should
they get squeeze?  If they should get squeeze, the
testing-proposed-update source will give them the wrong set of
packages after squeeze is released.

I believe those installing testing today should get squeeze and
continue to use squeeze after the release.  At least that is what I
expect when I install testing today.  I am sure others might believe
otherwise, and am not sure which view should have priority.

Happy hacking,
-- 
Petter Reinholdtsen