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

Bug#695531: marked as done (/Bugs/Developer#severities: misleading description of serious)

Your message dated Sun, 9 Dec 2012 23:09:21 +0100
with message-id <20121209220921.GA2243@radis.cristau.org>
and subject line Re: Bug#695531: /Bugs/Developer#severities: misleading description of serious
has caused the Debian Bug report #695531,
regarding /Bugs/Developer#severities: misleading description of serious
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
695531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695531
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: www.debian.org
Severity: normal

I was educated that the definition of severity level serious is subtly
wrong. It is currently defined on /Bugs/Developer#severities as:

| serious
|     is a severe violation of Debian policy (roughly, it violates a
|     "must" or "required" directive), or, in the package maintainer's or
|     release manager's opinion, makes the package unsuitable for release.

According to this definition any bug that strictly violates the Debian
policy is to be considered serious. This is wrong. The rc_policy.txt
overrides the Debian policy. This may not be considered "right", by
some, but it represents the current practise. It is essential for the
transparency of the Debian project to clearly document such policies.

Please consider the following replacement.

| serious
|     is a severe violation of Debian policy (roughly, it violation a
|     "must" or "required" directive), or, in the package maintainer's
|     opinion makes the package unsuitable for release. In any case the
|     release managers have the last word on what is or is not to be
|     considered serious.

Helmut

--- End Message ---
--- Begin Message --- 
On Sun, Dec  9, 2012 at 21:35:13 +0100, Helmut Grohne wrote:

> Package: www.debian.org
> Severity: normal
> 
> I was educated that the definition of severity level serious is subtly
> wrong. It is currently defined on /Bugs/Developer#severities as:
> 
> | serious
> |     is a severe violation of Debian policy (roughly, it violates a
> |     "must" or "required" directive), or, in the package maintainer's or
> |     release manager's opinion, makes the package unsuitable for release.
> 
> According to this definition any bug that strictly violates the Debian
> policy is to be considered serious.

No idea how you read that.  Or what you think "strictly violates" means.
There's no definition of what "severe" means here.  In practice, it
means "rc_policy".

Please drop this already.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: