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/001476.html | 75 +++++++++++++++++++++++++ 1 file changed, 75 insertions(+) create mode 100644 zarb-ml/mageia-webteam/2011-October/001476.html (limited to 'zarb-ml/mageia-webteam/2011-October/001476.html') diff --git a/zarb-ml/mageia-webteam/2011-October/001476.html b/zarb-ml/mageia-webteam/2011-October/001476.html new file mode 100644 index 000000000..064ff79de --- /dev/null +++ b/zarb-ml/mageia-webteam/2011-October/001476.html @@ -0,0 +1,75 @@ + + + + [Mageia-webteam] [Bug 3047] ASSIGNED status means + + + + + + + + + +

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

+ Marja van Waes + bugzilla-daemon at mageia.org +
+ Wed Oct 19 21:41:43 CEST 2011 +

+
+ +
https://bugs.mageia.org/show_bug.cgi?id=3047
+
+--- Comment #21 from Marja van Waes <marja11 at xs4all.nl> 2011-10-19 21:41:43 CEST ---
+@ Frédéric
+
+Thanks for your comment and for the search example (I wouldn't have managed to
+figure out how to do that)
+
+I like your proposal, but I know there are maintainers who use the "ASSIGNED"
+status to control there workflow, that is, they don't set a bug to that status
+before they actually start working on it. They would panic when they were
+forced to set the status to ASSIGNED as soon as they have triaged that the bug
+was assigned to them correctly
+
+I'm confident you have something better for them to control their workflow :)
+
+-- 
+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