diff options
Diffstat (limited to 'zarb-ml/mageia-bugsquad/attachments/20121101/b055b2a7')
| -rw-r--r-- | zarb-ml/mageia-bugsquad/attachments/20121101/b055b2a7/attachment-0001.html | 41 | ||||
| -rw-r--r-- | zarb-ml/mageia-bugsquad/attachments/20121101/b055b2a7/attachment.html | 41 |
2 files changed, 82 insertions, 0 deletions
diff --git a/zarb-ml/mageia-bugsquad/attachments/20121101/b055b2a7/attachment-0001.html b/zarb-ml/mageia-bugsquad/attachments/20121101/b055b2a7/attachment-0001.html new file mode 100644 index 000000000..9b2966619 --- /dev/null +++ b/zarb-ml/mageia-bugsquad/attachments/20121101/b055b2a7/attachment-0001.html @@ -0,0 +1,41 @@ +<html> + <head> + <meta content="text/html; charset=ISO-8859-1" + http-equiv="Content-Type"> + </head> + <body bgcolor="#FFFFFF" text="#000000"> + Le 01/11/2012 08:34, Marja van Waes a écrit : + <blockquote cite="mid:50922614.30600@xs4all.nl" type="cite"> + <pre wrap="">Hi everyone, + +Before I start going over old NEEDINFO bugs again: + +According to the triage guide, incomplete bugs should, if the +requested info isn't supplied, be closed as INVALID. + +I don't see anything about originally <b class="moz-txt-star"><span class="moz-txt-tag">*</span>valid<span class="moz-txt-tag">*</span></b> bugs, where later +additional information was requested (e.g. because it was filed +against cauldron and cauldron changed a lot, or because the involved +package was updated). + +I did close those as OLD if the reporter didn't reply. Was that good +to do in the first place? + +If it was good: I'm now wondering how I can keep myself from +accidentally closing reports that have <b class="moz-txt-star"><span class="moz-txt-tag">*</span>never<span class="moz-txt-tag">*</span></b> been valid, as OLD +instead of as INVALID, if I don't take a lot more time to read the +reports :/ + +Cheers, +Marja</pre> + </blockquote> + <br> + Well the triage guide was originally copy-paste from mdv, so we can + do whatever we want too.<br> + And beside for ours stats, or angry users, I guess make it simple + without detailing doesn't shock anyone.<br> + <br> + <br> + <br> + </body> +</html> diff --git a/zarb-ml/mageia-bugsquad/attachments/20121101/b055b2a7/attachment.html b/zarb-ml/mageia-bugsquad/attachments/20121101/b055b2a7/attachment.html new file mode 100644 index 000000000..9b2966619 --- /dev/null +++ b/zarb-ml/mageia-bugsquad/attachments/20121101/b055b2a7/attachment.html @@ -0,0 +1,41 @@ +<html> + <head> + <meta content="text/html; charset=ISO-8859-1" + http-equiv="Content-Type"> + </head> + <body bgcolor="#FFFFFF" text="#000000"> + Le 01/11/2012 08:34, Marja van Waes a écrit : + <blockquote cite="mid:50922614.30600@xs4all.nl" type="cite"> + <pre wrap="">Hi everyone, + +Before I start going over old NEEDINFO bugs again: + +According to the triage guide, incomplete bugs should, if the +requested info isn't supplied, be closed as INVALID. + +I don't see anything about originally <b class="moz-txt-star"><span class="moz-txt-tag">*</span>valid<span class="moz-txt-tag">*</span></b> bugs, where later +additional information was requested (e.g. because it was filed +against cauldron and cauldron changed a lot, or because the involved +package was updated). + +I did close those as OLD if the reporter didn't reply. Was that good +to do in the first place? + +If it was good: I'm now wondering how I can keep myself from +accidentally closing reports that have <b class="moz-txt-star"><span class="moz-txt-tag">*</span>never<span class="moz-txt-tag">*</span></b> been valid, as OLD +instead of as INVALID, if I don't take a lot more time to read the +reports :/ + +Cheers, +Marja</pre> + </blockquote> + <br> + Well the triage guide was originally copy-paste from mdv, so we can + do whatever we want too.<br> + And beside for ours stats, or angry users, I guess make it simple + without detailing doesn't shock anyone.<br> + <br> + <br> + <br> + </body> +</html> |