summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/20100925/001152.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-discuss/20100925/001152.html')
-rw-r--r--zarb-ml/mageia-discuss/20100925/001152.html159
1 files changed, 159 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20100925/001152.html b/zarb-ml/mageia-discuss/20100925/001152.html
new file mode 100644
index 000000000..1c7b00295
--- /dev/null
+++ b/zarb-ml/mageia-discuss/20100925/001152.html
@@ -0,0 +1,159 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-discuss] Think about bugzilla monitoring?
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Think%20about%20bugzilla%20monitoring%3F&In-Reply-To=%3CAANLkTi%3D1y1O5GtL%3D%3DiqqC5M%3D0UvJnHCm9EFXLiAGuASG%40mail.gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="001150.html">
+ <LINK REL="Next" HREF="001191.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-discuss] Think about bugzilla monitoring?</H1>
+ <B>Ahmad Samir</B>
+ <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20Think%20about%20bugzilla%20monitoring%3F&In-Reply-To=%3CAANLkTi%3D1y1O5GtL%3D%3DiqqC5M%3D0UvJnHCm9EFXLiAGuASG%40mail.gmail.com%3E"
+ TITLE="[Mageia-discuss] Think about bugzilla monitoring?">ahmadsamir3891 at gmail.com
+ </A><BR>
+ <I>Sat Sep 25 06:57:51 CEST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001150.html">[Mageia-discuss] who knows about site mageia-br?
+</A></li>
+ <LI>Next message: <A HREF="001191.html">[Mageia-discuss] Think about bugzilla monitoring?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1152">[ date ]</a>
+ <a href="thread.html#1152">[ thread ]</a>
+ <a href="subject.html#1152">[ subject ]</a>
+ <a href="author.html#1152">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On 24 September 2010 14:58, Juergen Harms &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">Juergen.Harms at unige.ch</A>&gt; wrote:
+&gt;<i> Picking up from where Mageia forked off, many things activities look like
+</I>&gt;<i> continuity from Mandriva Linux. But forking is also a challenge to find not
+</I>&gt;<i> too hard to implement improvements - such as &quot;bugzilla monitoring&quot;.
+</I>&gt;<i>
+</I>&gt;<i> I think I am not the only one who frequently felt frustrated submitting yet
+</I>&gt;<i> another bug, knowing that it had more 50% of chance to disappear the
+</I>&gt;<i> &quot;oubliettes&quot;. I think there is an objective question: if bugs are not
+</I>&gt;<i> followed up, that should not just happen by accident - there should be an
+</I>&gt;<i> explicit and justified decision. There is also a subjective question: a user
+</I>&gt;<i> who went through the pains to write a good bug report should get a feedback
+</I>&gt;<i> with a followup, even if there are no &quot;comments&quot; in the bugzilla data base.
+</I>&gt;<i>
+</I>
+Well, let me put it this way, a bug report will go unfixed in the
+following cases:
+- Triage work ends when the bug report is assigned to the maintainer;
+if the bug has no maintainer then the chances that it'll get fixed are
+a bit lower (some packages have no maintainer but are used by a lot of
+users so it gets fixed any way)
+
+- The package has a maintainer but he's overworked and has a huge
+backlog, unfortunately that happens to everyone, in this case posting
+a new comment in the report should bring it back up in his list;
+pinging a bug report is the reporter's responsibility (triage team is
+always understaffed so to speak, too many bug reports, too few people
+to triage them all); so if after say a week of reporting a bug you get
+no response from the maintainer feel free to ask in the report.
+
+It's always nice to acknowledge a bug report but unfortunately that
+doesn't always happen... you have to understand that a lot of bug
+reports go in per day (it also seasonal, i.e. towards the end of the
+development cycle the amount of bug reports increases considerably).
+
+Another point is, there isn't a bugzilla where some bug reports don't
+go forgotten, again ideally this shouldn't happen, but there's ideal
+and there's what really happens :/
+
+&gt;<i> Some ideas: have a &quot;lost bug advocate&quot;? create a team - just like the
+</I>&gt;<i> &quot;triage team&quot; that feels responsible for bugs not to disappear? (different
+</I>&gt;<i> from the, but talking to, maybe overlapping the triage team, leaning on the
+</I>&gt;<i> &quot;dev&quot; - in Mageia it will be a volonteer, even more important - to whom a
+</I>&gt;<i> bug is assigned) - proposing and justifying which bugs - for the time being
+</I>&gt;<i> - will have no follow up), creating some commented statistics on the fate of
+</I>&gt;<i> bugs - good for QA, but also for PR about Mageia? trigger an alarm if too
+</I>&gt;<i> many bugs remain un-resolved? - always assuming that enough active
+</I>&gt;<i> contribution can be recruited from the temp. wiki list. I also believe that,
+</I>&gt;<i> for Mageia, the situation is different. In Mandriva, I guess that some
+</I>&gt;<i> (many?) of these acitivities were done by staff of the QA group - in Mageia
+</I>&gt;<i> an alternative is needed.
+</I>&gt;<i>
+</I>&gt;<i> Maybe Mandriva had something like this - if yes, it was too well hidden.
+</I>
+As I said, pining a bug report to bring to the attention of the
+package maintainer is the reporter's responsibility, at least given
+the fact that he's suffering from that bug, i.e. he has a strong
+motive.
+
+You also have to bear in mind that sometimes a bug reporter doesn't
+remember, or doesn't bother, to close a report when a bug he'd
+reported has been fixed.
+
+Also note that before a new release a lot of devs/packagers go through
+all the reports assigned to them (depending on their time of course if
+they're contributors doing dev work in their free time, or employees
+with other more critical things to fix before a release).
+
+&gt;<i> _______________________________________________
+</I>&gt;<i> Mageia-discuss mailing list
+</I>&gt;<i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">Mageia-discuss at mageia.org</A>
+</I>&gt;<i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-discuss">https://www.mageia.org/mailman/listinfo/mageia-discuss</A>
+</I>&gt;<i>
+</I>
+
+
+--
+Ahmad Samir
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001150.html">[Mageia-discuss] who knows about site mageia-br?
+</A></li>
+ <LI>Next message: <A HREF="001191.html">[Mageia-discuss] Think about bugzilla monitoring?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1152">[ date ]</a>
+ <a href="thread.html#1152">[ thread ]</a>
+ <a href="subject.html#1152">[ subject ]</a>
+ <a href="author.html#1152">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss
+mailing list</a><br>
+</body></html>