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

Bug#1010415: marked as done (www.debian.org: please slightly clarify description of 'grave' bug severity)

Your message dated Fri, 08 Nov 2024 02:53:47 +0000
with message-id <672d7d3b5a7d6_1b7a697173c0555d9@godard.mail>
and subject line Bug#1010415 fixed in www.debian.org
has caused the Debian Bug report #1010415,
regarding www.debian.org: please slightly clarify description of 'grave' bug severity
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.)


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

Severity: wishlist
On https://www.debian.org/Bugs/Developer, the description for the severity level of grave reads, "makes the package in question unusable or mostly so, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package."
I believe that this confuses our users (and sometimes developers), who read that and think to themselves, "well this makes the package unusable FOR ME, therefore the severity must be grave." It's clear from the description of 'important' ("a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone") that the intention is for grave to apply to issues that make the package unusable FOR MOST USERS. I'm filing this bug because I keep seeing bugs filed as grave that make this mistake.
Therefore, I suggest modifying the language of the grave severity level description to read (with the new text between asterisks), "makes the package in question unusable *by most users*, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package.", with "or mostly so" being removed.
Reportbug's description for grave is "makes the package in question unusable by most or all users, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package."  Modifying the website language as I suggested would make it closer match the reportbug language.
--- End Message ---
--- Begin Message --- 
Hello,

Bug #1010415 in www.debian.org reported by you has been fixed in the Git repository.
You can see the commit message below and you can check the diff of the fix at:

https://salsa.debian.org/webmaster-team/webwml/-/commit/e5f7f972c0a451cd076cf53f9bb125d9f11003ae

------------------------------------------------------------------------
english/Bugs/Developer.wml: Use grave bug desc with reportbug

Make the description of Severity: grave bug to be the same as
text in reportbug(1) tool as of reportbug/13.0.1.

See https://bugs.debian.org/1010415 for the suggestion.

Closes: #1010415
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1010415

--- End Message ---
Reply to: