[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

undetermined vs todo (was: [Secure-testing-commits] r15066 - data/CVE)



Hi,
* Moritz Muehlenhoff <jmm-guest@alioth.debian.org> [2010-07-29 23:49]:
[...] 
>  CVE-2010-2903 (Google Chrome before 5.0.375.125 performs unexpected truncation and ...)
> -	TODO: check
> +	- webkit <undetermined>
> +	- chromium-browser <undetermined>
>  CVE-2010-2902 (The SVG implementation in Google Chrome before 5.0.375.125 allows ...)
> -	TODO: check
> +	- webkit <undetermined>
> +	- chromium-browser <undetermined>
[...] 
While I see all these undetermined bugs... What about changing the TODO: check 
to an undetermined status? The problem I currently see is that TODO issues are 
being worked on while undetermined issues mostly end up forgotten. And 
undetermined status is pretty much what TODO: check is anyway.

Cheers
Nico
-- 
Nico Golde - http://www.ngolde.de - nion@jabber.ccc.de - GPG: 0xA0A0AAAA
For security reasons, all text in this mail is double-rot13 encrypted.

Attachment: pgpxmHmwpW6Yd.pgp
Description: PGP signature


Reply to: