Hello Green (is this your real name? it's nice to know who you're talking to),
On Thu, Oct 8, 2009 at 06:20, green <greenfreedo...@gmail.com> wrote: > Package: reportbug > Version: 3.48 > Severity: normal > > The description for the 'grave' severity in reportbug should indicate that it > is _not_ for _serious_ data loss, like: "causes non-serious data loss". The severities in reportbug are the ones defined[1] by the BTS, so I'm not going to branch from their description. If you want them to be changed, your should talk to BTS maintainers first, then downstream to us. Closing this bug report now. [1] http://www.debian.org/Bugs/Developer#severities > I was reporting a bug (550103) for a program that did cause data loss by not > writing user inputted data to the filesystem. That data therefore becomes > unrecoverable--that is 'serious data loss'. When reporting the bug, I chose > 'grave' because it mentioned 'data loss' and I did not feel that 'critical' > severity was correct because the data loss was not catastrophic. When > reportbug asked for justification, the only data loss option is 'non-serious', > so I was forced to use 'unknown' which lowered the severity to 'normal'. I > should have used 'critical' and 'causes serious data loss', hence the > suggested > description change. No, the correct severity is 'grave': 'critical' is far too higher for a program not saving its own files. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
