diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101016/001241.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101016/001241.html | 104 |
1 files changed, 104 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101016/001241.html b/zarb-ml/mageia-dev/20101016/001241.html new file mode 100644 index 000000000..3b00c29d6 --- /dev/null +++ b/zarb-ml/mageia-dev/20101016/001241.html @@ -0,0 +1,104 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] How will be the realese cycle? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3Ci9d2l7%24fm9%241%40dough.gmane.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001242.html"> + <LINK REL="Next" HREF="001234.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How will be the realese cycle?</H1> + <B>Marc Paré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3Ci9d2l7%24fm9%241%40dough.gmane.org%3E" + TITLE="[Mageia-dev] How will be the realese cycle?">marc at marcpare.com + </A><BR> + <I>Sat Oct 16 22:41:11 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001242.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="001234.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1241">[ date ]</a> + <a href="thread.html#1241">[ thread ]</a> + <a href="subject.html#1241">[ subject ]</a> + <a href="author.html#1241">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 2010-10-16 15:52, Renaud MICHEL a écrit : +><i> On samedi 16 octobre 2010 at 21:29, Marc Paré wrote : +</I>>><i> There would be no middle man. Once the middle-man could replicate the +</I>>><i> bug and verify the bug with other users, then the middle-man would +</I>>><i> submit to bugzilla. That's it. From there on, the middle-man will take +</I>>><i> care of testing requests from devs. +</I>><i> +</I>><i> That would only work for pure software bugs. +</I>><i> If the bug is hardware related, it is unlikely that the "middle man" will be +</I>><i> able to reproduce it. For those we really need the input from the real bug +</I>><i> reporter. +</I>><i> +</I>><i> And for software bugs, the "middle man" would have to reproduce the software +</I>><i> environment of the reporter, which may be complicated if he installed +</I>><i> software from third party (or worse, proprietary software). +</I>><i> Sometimes the problem is obvious and only related to a single package, and +</I>><i> for such case a forum with some contributors reproducing the bug and then +</I>><i> submitting a bug report may work. +</I>><i> But if the problem is related to a particular combination of packages then +</I>><i> the "middle man" could spend a considerable amount of time replicating the +</I>><i> reporter particular configuration before he can actually reproduce the bug. +</I>><i> +</I>><i> I think it may work if those "bug friends" (don't remember who proposed that +</I>><i> name) only take for themselves the simple, one package, software only bugs, +</I>><i> and suggest to the reporter to create himself a bugreport (eventually +</I>><i> providing assistance if the reporter has never done it before) describing +</I>><i> his problem, because the devs will really need his feedback first hand. +</I>><i> That forum would be an easier entry point than bugzilla for users not +</I>><i> familiar with bugreports. +</I>><i> +</I> +Yes you are perfectly right. This is where the the bug report would be +ramped up to the bugzilla stage, and at the point, the reporter would +have obviously shown an interest in the resolution/fix of the bug. This +would in effect would create a mentorhsip/reporter relationship and a +great training opportunity for the reporter. We would then have, by +default, a mentorship programme in the "Report a bug" forum that may +eventually form other "bug friends" This would be a great opportunity +for Mageia to teach reporters how to use bugzilla. + +IMHO, this would still be a simple way of dealing with normal users who +do not want to involve themselves any more than reporting a bug. And for +those who develop a taste for furthering their knowledge of the process +of bug reporting, the "bug friend" could then mentor this person ... who +could eventually become a "bug friend" himself/herself. + +Marc + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001242.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="001234.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1241">[ date ]</a> + <a href="thread.html#1241">[ thread ]</a> + <a href="subject.html#1241">[ subject ]</a> + <a href="author.html#1241">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev +mailing list</a><br> +</body></html> |