From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-webteam/2011-October/001473.html | 98 +++++++++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 zarb-ml/mageia-webteam/2011-October/001473.html (limited to 'zarb-ml/mageia-webteam/2011-October/001473.html') diff --git a/zarb-ml/mageia-webteam/2011-October/001473.html b/zarb-ml/mageia-webteam/2011-October/001473.html new file mode 100644 index 000000000..1295d36fd --- /dev/null +++ b/zarb-ml/mageia-webteam/2011-October/001473.html @@ -0,0 +1,98 @@ + + + + [Mageia-webteam] [Bug 3047] ASSIGNED status means + + + + + + + + + +

[Mageia-webteam] [Bug 3047] ASSIGNED status means

+ Frédéric Buclin + bugzilla-daemon at mageia.org +
+ Wed Oct 19 20:52:24 CEST 2011 +

+
+ +
https://bugs.mageia.org/show_bug.cgi?id=3047
+
+Frédéric Buclin <LpSolit at aim.com> changed:
+
+           What    |Removed                     |Added
+----------------------------------------------------------------------------
+                 CC|                            |LpSolit at aim.com
+
+--- Comment #20 from Frédéric Buclin <LpSolit at aim.com> 2011-10-19 22:52:24 CEST ---
+Adding a new bug status doesn't necessarily help maintainers fix their bugs
+faster. :) If assignees do not use the new bug status as you wish, this just
+make things harder to manage. For you information, Bugzilla 4.0 renamed NEW as
+CONFIRMED, and ASSIGNED as IN_PROGRESS to better reflect what they mean
+(Mageia's Bugzilla won't be affected as these new bug statuses are only for new
+installations, not for those which are upgrading).
+
+There are two things which could help the triage team:
+
+1) Pester maintainers to triage bugs assigned to them. Bugzilla has a whining
+system which works as follows: whineatnews.pl can be run as a cron job (e.g.
+once a week) and it will send an email to all assignees who didn't touch their
+bugs in the last X days, where X is configurable from the Parameters page. Only
+bugs left with status NEW and REOPENED are concerned. If assignees complain
+about these weekly emails, tell them to either reassign their bugs to squad, or
+change the bug status to ASSIGNED (the whining system doesn't pester about bugs
+with the status set to ASSIGNED). This is a nice way to force them to triage
+bugs assigned to them.
+
+2) You can query for bugs which haven't been touched by their assignee in the
+last Y days. For instance, to get all open bugs in the Mageia product where the
+assignee didn't do anything in the last 15 days:
+
+https://bugs.mageia.org/buglist.cgi?emailassigned_to1=1&query_format=advanced&field0-0-0=owner_idle_time&email1=bugsquad%40mageia.org&type0-0-0=greaterthan&value0-0-0=15&resolution=---&product=Mageia&emailtype1=notequals
+
+If you are curious to see how I did it, simply click the "Edit Search" link at
+the bottom of the list, and you will see which fields I filed. This is another
+good way to keep track of inactive bugs.
+
+-- 
+Configure bugmail: https://bugs.mageia.org/userprefs.cgi?tab=email
+------- You are receiving this mail because: -------
+You are on the CC list for the bug.
+
+ + + +
+

+ +
+More information about the Mageia-webteam +mailing list
+ -- cgit v1.2.1