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

Bug#399331: marked as done (please define howto set urgency)



Your message dated Sun, 14 Jan 2007 14:24:42 -0600
with message-id <87vej9uzjp.fsf@glaurung.internal.golden-gryphon.com>
and subject line Bug#399331: please define howto set urgency
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
package: debian-policy
version: 3.7.2.2
severity: wishlist

Hi,

http://www.us.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgency 
doesn't give any indication how the urgency should be set. So it's arbitrary 
to the maintainers will? I don't think so :)


regards,
	Holger

Attachment: pgpeY8RTE7Cua.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
Hi,
On Sun, 19 Nov 2006 11:39:24 +0100, Holger Levsen
<debian@layer-acht.org> said:  

> http://www.us.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Urgencydoesn't
> give any indication how the urgency should be set. So it's arbitrary
> to the maintainers will? I don't think so :)

        Err, why not? Setting the value is indeed up to the developer,
 and depends on the state of the release, how important the developer
 judges the bug fixes and other changes in the new upload are, and a
 whole lot of other factors that can't be easily laid down in a
 standard.

        I would much rather leave it open to the judgement of
 developers than try to put in a lot of effort to get something
 written down that can handle all possible cases and ramifications
 thereof. If you disagree, please identify what the problems are, and
 why the solution to the problems need be writ in stone in policy.

        manoj
-- 
"Friends don't let friends run Xenix." Stephen J. Friedl
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

--- End Message ---

Reply to: