blob: dce8bb567b85a0fd15936966c366460f7d6b204d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
|
<!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=%3Ci9cuep%24rf7%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="001237.html">
<LINK REL="Next" HREF="001239.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=%3Ci9cuep%24rf7%241%40dough.gmane.org%3E"
TITLE="[Mageia-dev] How will be the realese cycle?">marc at marcpare.com
</A><BR>
<I>Sat Oct 16 21:29:29 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001237.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="001239.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1238">[ date ]</a>
<a href="thread.html#1238">[ thread ]</a>
<a href="subject.html#1238">[ subject ]</a>
<a href="author.html#1238">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 2010-10-16 12:36, Ahmad Samir a écrit :
><i>
</I>><i> But generally reporting bugs by proxy is always a bad idea, unless the
</I>><i> guy who'll play middle-man can reproduce the exact same bug on his own
</I>><i> box. You see, triage team / package maintainer / dev will ask for info
</I>><i> about the bug, more than once depending on the bug itself; now Mr.
</I>><i> middle-man will have to go to and fro a lot of times, taking info from
</I>><i> the user and posting it in bugzilla then taking questions/info from
</I>><i> the bugzilla and conveying it to the user; now that's a tedious and
</I>><i> tiresome job that's very prone to failure. (it's like a friend being
</I>><i> sick and instead of him going to the doctor he sends you on his behalf
</I>><i> because "you know the symptoms" :)).
</I>><i>
</I>><i> It's much better to help the user formulate a useful bug report,
</I>><i> that's easier / more productive for all involved parties.
</I>><i>
</I>
There would be no middle man. Once the middle-man could replicate the
bug and verify the bug with other users, then the middle-man would
submit to bugzilla. That's it. From there on, the middle-man will take
care of testing requests from devs.
As far as reporting back to the original user who reported the bug, as
an extra gesture of kindness, the middle-man would just post on the
"Report a bug" forum that the bug has been quashed or is still under
review ... but not to the user but to the "Report a bug" forum.
The idea is to keep the flow of possible bug reports coming in an
organised way. The middle-man would have to be someone with a little
more experience than that of a new user and also someone who has an
interest in working this way. We will get more bug reports from users by
keeping it simple and easy.
Marc
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001237.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="001239.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1238">[ date ]</a>
<a href="thread.html#1238">[ thread ]</a>
<a href="subject.html#1238">[ subject ]</a>
<a href="author.html#1238">[ 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>
|
