On Sat, 9 Jan 2010 14:13:50 -0500 Michael Gilbert wrote: > On Sat, 9 Jan 2010 17:26:43 +0100 Francesco Poli wrote: > > > On Fri, 8 Jan 2010 17:59:52 -0500 Michael Gilbert wrote: > > > > [...] > > > I propose to show all unspecified urgencies as low in the tracker. [...] > > This would force the meaning of an unset urgency into being equivalent > > to a low urgency. > > IMHO, this would reduce the expressive power of the security tracker: > > to me, an unset urgency basically means "unclassified"; that is to say, > > something that could be low, medium, or even high, but requires further > > thinking before one can decide which is the correct category. > > Thank you very much for your feedback. You're welcome. > The new <undetermined> tag is > actually indended for the case you describe above. If the triager has > done enough work to decide that <undetermined> is not appropriate, then > they must have enough information to appropriately categorize the > issue. Hence, if they choose not to set the urgency, then it indicates > that they did not find it to be of elevated urgency. Wait, I must confess that I am losing you here. If I understand correctly, in the thread titled "Documentation for the new <undetermined> tag" you explained that this tag is intended for cases where it's not yet clear whether a vulnerability is <fixed> or <unfixed> in a given version of a package. Now you are talking about another <undetermined> tag. Or about the same tag? In the current thread, you proposed to convert all "blank urgencies" to "undetermined". Moritz replied "No way". At that point you stated that you yourself changed your mind and agree with Moritz that "<undetermined> is definitely not right for these cases". Now you again seem to claim that the <undetermined> tag is the replacement for blank (i.e.: unset, no?) urgency cases... Could you please clarify? -- http://www.inventati.org/frx/progs/scripts/pdebuild-hooks.html Need some pdebuild hook scripts? ..................................................... Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
Attachment:
pgpaY5ku74geX.pgp
Description: PGP signature