Bug#321102: KMail with RC-Bugs moved to testing?
On Tuesday 25 April 2006 02:48, Bastian Venthur wrote:
> I noticed KMail moving to testing, although it has grave bugs open.
> Was this a mistake? I always thought packages with RC Bugs don't
> enter testing until they're fixed?
>
> Looking at #321102, I noticed that "found in version" is set to
> various old versions but not to the current one (which is not that
> old BTW). If this affected the migration to testing, it would look
> like cheating to me in order to get the current PIM into testing at
> all costs.
>
> I might be biased since I'm the reporter of some of the RC-bugs, but
> the according upstream-bugs are still open (and still has 780 votes),
> so I don't see a reason to assume this bug was somehow fixed. I
> suggest to keep the bug open for every current version until the
> according upstream-bug is closed. Since this is currently the only
> grave bug in upstreams BTS I think the chances that upstream will
> forget about the bug are pretty low.
Packages are allowed in to testing if the RC bug count on the version in
testing is higher or equal to the RC bug count on the version in
unstable. Since upstream bug reports indicated that the problems in
Kmail go back to KDE 3.4 at least (hence all the "found in" additions),
there was no point in holding kdepim 3.5 out of testing, since there
was no regression. It doesn't matter if the very latest package is not
marked "found in" for counting purposes; if the bug is open, then this
is assumed to be the case. Indeed, some people strongly suspect that
kdepim 3.5.2 fixed the problems, though since this isn't certain, we
should keep the bugs open for now. Still, this makes letting kdepim
into testing worthwhile.
Cheers,
Christopher Martin
Reply to: