1 |
On 06/23/12 at 09:37PM +0200, Christian Ruppert wrote: |
2 |
> Guys, |
3 |
> |
4 |
> that was a test. I didn't expect it to write "You will get this message once a |
5 |
> day until you've dealt with these" so don't take it too serious. I'm sorry about |
6 |
> that but i just saw that *a lot* of bugs have been changed from CONFIRMED to IN_PROGRESS.. |
7 |
> sorry.. but *that* is more than just wrong.. that is ... |
8 |
> If you're scared or annoyed than you should at least complain first. |
9 |
> |
10 |
> You should rather try to fix bugs instead of confusing the *users* by marking |
11 |
> bugs as IN_PROGRESS when nobody actually works on it at all. |
12 |
> |
13 |
> So again: There will be no daily Bugzilla whines and esp. no global whines! |
14 |
> We *may* enable it as a yearly job or so but there are no serious plans yet! |
15 |
> |
16 |
> -- |
17 |
> Regards, |
18 |
> Christian Ruppert |
19 |
> Gentoo Linux developer, Bugzilla administrator and Infrastructure member |
20 |
> Fingerprint: EEB1 C341 7C84 B274 6C59 F243 5EAB 0C62 B427 ABC8 |
21 |
|
22 |
It just turned out that at least parts of that template seem to be outdated. |
23 |
|
24 |
E.g. #3: |
25 |
(3) You decide the [% terms.bug %] belongs to you, but you can't solve it |
26 |
this moment. Accept the [% terms.bug %] by setting the status to |
27 |
[% display_value("bug_status", "IN_PROGRESS") %]. |
28 |
|
29 |
That was actually meant for when we had the ASSIGNED status for which it would |
30 |
make more sense. |
31 |
|
32 |
Again: Don't take it too serious, if it helps to remind you that's fine but |
33 |
ignore anything else. |
34 |
|
35 |
-- |
36 |
Regards, |
37 |
Christian Ruppert |
38 |
Gentoo Linux developer, Bugzilla administrator and Infrastructure member |
39 |
Fingerprint: EEB1 C341 7C84 B274 6C59 F243 5EAB 0C62 B427 ABC8 |