[Mono-bugs] [Bug 57703][Nor] Changed - MCS emits invalid IL for events on an interface
Wed, 28 Apr 2004 10:29:05 -0400 (EDT)
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by firstname.lastname@example.org.
--- shadow/57703 2004-04-28 09:25:38.000000000 -0400
+++ shadow/57703.tmp.4494 2004-04-28 10:29:05.000000000 -0400
@@ -98,6 +98,36 @@
Critical is for major regressions -- eg, bootstrap fails
Major/Blocker is also for regressions -- it is sorta rare these days
Normal is where most bugs should go.
Anything below is for annoyences -- eg, we emit the wrong error
message; we should emit an error message but have an unhandled
exception; we dont flag an error.
+------- Additional Comments From email@example.com 2004-04-28 10:29 -------
+Not to be the 'hey where did you find that crack' pain in the ass,
+but, dude, where did you find that crack?
+here is a quote for you:
+Critical - We should fix and push an update immediately. This will
+mostly be used for security fixes.
+Blocker - crashes, loss of data, severe memory leak
+Major - A major part of the component is nonfunctional.
+Normal - A minor part of the component is nonfunctional.
+Minor - The component mostly works, but causes some irritation to
+users. A workaround should usually exist.
+Cosmetic - The component works with 100% functionality, but has
+visible typos, etc.
+Wishlist - Generally a feature request for functionality the program
+doesn't already have. These can be useful as guides for future product
+Now, obviously this bug seem to be either major or blocker based on
+Where did this info come from? why, it came from the url located here:
+http://bugzilla.ximian.com/bug_status.html#priority also where you are
+brought when you click on the link for Priority.
+This list seems to be pretty much the defacto standard as far as I can
+tell across all the bugzilla installations.