On Sat, Dec 27, 2008 at 04:11:35PM +1100, Ben Finney wrote:
The decision of whether a bug is release-critical or not is for the
release managers to make, using the various properties of the bug
(including but *not* limited to its severity) as input to that
decision. They can, in fact, make
On Sat, 27 Dec 2008, Ben Finney wrote:
So, it's not correct for anyone but a release manager to decide
“this bug is/is not release-critical, so I'll change the severity”;
that is a perversion of the meaning of the severity field.
That's not quite true. See below.
You can argue about whether
Processing commands for cont...@bugs.debian.org:
package general
Ignoring bugs not assigned to: general
reassign 509732 doc-debian
Bug#509732: Debian policy doesn't feature RC bugs
Bug reassigned from package `general' to `doc-debian'.
thanks
Stopping processing here.
Please contact me
package general
reassign 509732 doc-debian
thanks
José Luis González wrote:
This makes it impossible to report a bug with RC severity in
the Bug Tracking System that permits RC bugs to remain in Debian when
the report is closed incorrectly and nobody notices before it is
archived (please see
José Luis González jlgon...@ya.com writes:
System. This makes it impossible to report a bug with RC severity in
the Bug Tracking System that permits RC bugs to remain in Debian when
the report is closed incorrectly and nobody notices before it is
archived (please see bug #227941.) Since the
On Thu, 25 Dec 2008 17:13:54 +0200
Kalle Kivimaa kil...@debian.org wrote:
José Luis González jlgon...@ya.com writes:
Why on earth would #227941 be anything but a wishlist? It is very easy
to reopen an archived bug, all you need to do is unarchive it first.
It is indeed a wishlist. Please, see
On Thu, 25 Dec 2008, José Luis González wrote:
If a problem is RC, it should be marked as RC. If the BTS manages
pseudopackages, a bug in a pseudopackage that is RC should be marked
as RC in the BTS.
The BTS has nothing to do with deciding whether particular bugs are
release critical or not.
Don Armstrong d...@debian.org writes:
On Thu, 25 Dec 2008, José Luis González wrote:
If a problem is RC, it should be marked as RC. If the BTS manages
pseudopackages, a bug in a pseudopackage that is RC should be
marked as RC in the BTS.
The BTS has nothing to do with deciding whether
Package: general
Severity: important
The Debian Policy Manual doesn't feature the Debian Bug Tracking
System. This makes it impossible to report a bug with RC severity in
the Bug Tracking System that permits RC bugs to remain in Debian when
the report is closed incorrectly and nobody notices
This makes it impossible to report a bug with RC severity in
the Bug Tracking System that permits RC bugs to remain in Debian when
the report is closed incorrectly and nobody notices before it is
archived (please see bug #227941.) Since the problem is only specific
to that bug, it would
10 matches
Mail list logo
