John Goerzen writes: > On Tue, Oct 07, 2003 at 07:18:41PM +0200, Matthias Klose wrote: > > The e-mail I sent made several exceptions from the freeze, one of them > > fixing RC reports. So yes, you are supposed to fix these problems > > yourself. As I introduced this RC in 0.5.1-5.1, I fixed it in > > 0.5.1-5.2. > > Which is nice, but still does not explain why the freeze is necessary. I > don't understand the reason for it.
Packages, that are too young are not considered for migration to testing. As these packages have a dependency on "python (>=2.3)", they need to be migrated together with the migration to the default python version. IIRC it's possible for the release managers to override the constraints for some packages, but it gets tedious if many are affected. Matthias