On Tue, Nov 01, 2005 at 11:00:46AM +0100, Henning Makholm wrote: > No it's not. > > RC bug, still in testing -> fixing this is very important, because > it may hold up the testing migration of other packages. > > RC bug, not in testing -> fixing this only affects this one > package, and is therefore not so urgent. If the package isn't in testing, anything that depends on it isn't either, so you can still be affecting more than one package. Also, the above talks about its effect on other maintainers; you might also consider the effect on (potential) users of your package: in the former case "fixing this isn't that important, because users can just use the version in testing", while the latter is "fixing this is very important, because users don't have any recent version to use". Personally, I'd go for "RC bug -> fixing this is very important and urgent", and end there, though. Maybe it helps to look at it this way: testing tries to match unstable, while filtering out the crap; the more crap there is in unstable the harder that is and the more likely it is the filter will get clogged. Cheers, aj
Attachment:
signature.asc
Description: Digital signature