Re: Why are new package versions depending on libc6 in unstable?
>>"Steve" == Steve Langasek <firstname.lastname@example.org> writes:
Steve> Then perhaps it would help if there were some commonly
Steve> agreed-upon, objective criteria used to determine when a
Steve> package is ready for unstable as opposed to experimental?
Steve> (Projected number of RC bugs, optimal duration of transition
Steve> period, size of userbase...) This could at least help users
Steve> know what they're getting -- both in terms of how broken
Steve> unstable might be, and how out-of-date testing might be.
This is very hard, if not impossible, to determine a
priori. Unless someone hands me a crystall ball ;-)
Kent's Heuristic: Look for it first where you'd most like to find it.
Manoj Srivastava <email@example.com> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C