[Bug 559017] New: add new severity -- regression
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.novell.com/show_bug.cgi?id=559017 http://bugzilla.novell.com/show_bug.cgi?id=559017#c0 Summary: add new severity -- regression Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Bugzilla AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bluedzins@wp.pl QAContact: novbugzilla-bugs@forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux 2.6.27.37-0.1-default; X11; x86_64) KHTML/3.5.10 (like Gecko) SUSE New category of severity "regression" would allow to track more easily regression bugs. The problem is no matter how you express you are confident that opensuse X.Y is the best version so far, practice shows the regression ruins reputation of distro (opensuse). The principle should be that version X.Y+1 has no more bugs than version X.Y. Unfortantely for opensuse this principle didn't and does not hold. Reproducible: Always -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.novell.com/show_bug.cgi?id=559017 http://bugzilla.novell.com/show_bug.cgi?id=559017#c1 Marcus Meissner <meissner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |meissner@novell.com Resolution| |WONTFIX --- Comment #1 from Marcus Meissner <meissner@novell.com> 2009-11-30 16:11:23 UTC --- Regression bugs are also bugs... we are not tracking them seperately and will not start doing so. There is just no difference between a new bug and a regression bug, both need to be evaluated and if necessary fixed. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.novell.com/show_bug.cgi?id=559017 http://bugzilla.novell.com/show_bug.cgi?id=559017#c2 --- Comment #2 from Maciej Pilichowski <bluedzins@wp.pl> 2009-11-30 16:29:06 UTC --- Regression bug is of course bug, but it is more specific.
There is just no difference between a new bug and a regression bug
Actually there is -- if you introduce new filesystem and it will appear the algorithm is buggy, well, only those users will be affected who will choose this filesystem. But if you introduce bug to ext3 (for example) a lot of users will be affected. In other words -- if a bug appears in new feature, there is no new feature really, so the loss is minimal. When new bug is introduced to an old feature it means the already established systems/workflows are corrupted. My point was to better prioritize them -- regression bugs first, bugs in introduced features second. Otherwise you get what you have now -- regression to regressions, and so on. 11.2 is less reliable than 10.3 and 10.3 is less reliable than 10.2 (in hardware support issues). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com