Re: Bug mass filling
On Tue, 24 Oct 2006 13:49:01 -0400, Hubert Chan <firstname.lastname@example.org> said:
> On Mon, 23 Oct 2006 13:46:23 -0500, Manoj Srivastava
> <email@example.com> said: [...]
>>> and for policy:
>>> These classifications are roughly equivalent to the bug severities
>>> serious (for must or required directive violations), minor, normal
>>> or important (for should or recommended directive violations) and
>>> wishlist (for optional items).  However, this is not a direct
>>> mapping, and the release managers determine which violations are
>>> considered release-critical.
>> where does release criticality jump in here from? Policy has no
>> mention of RC in this context, I see no reason to suddenly inject
> Well, I did say that it was a very rough draft. ;)
> Second try:
> "... However, this is not a direct mapping, and the release
> managers determine the severity of each violation."
Direct mapping of *WHAT*? are you falling into the assumption
that serious == RC? Why?
Hard work never killed anybody, but why take a chance? Charlie
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C