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
93
|
<!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=%3Ci9i3ev%243bs%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="001264.html">
<LINK REL="Next" HREF="001256.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=%3Ci9i3ev%243bs%241%40dough.gmane.org%3E"
TITLE="[Mageia-dev] How will be the realese cycle?">marc at marcpare.com
</A><BR>
<I>Mon Oct 18 20:25:34 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001264.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="001256.html">[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1275">[ date ]</a>
<a href="thread.html#1275">[ thread ]</a>
<a href="subject.html#1275">[ subject ]</a>
<a href="author.html#1275">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le 2010-10-18 04:26, Wolfgang Bornath a écrit :
><i> 2010/10/18 Marc Paré<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">marc at marcpare.com</A>>:
</I>>><i>
</I>>><i> Thanks Michael for the note. This is why I am in favour of streamlining the
</I>>><i> reporting of bugs from the user side and not the dev. Devs should always
</I>>><i> count on seeing bugs reported on bugzilla and nothing more. However, on the
</I>>><i> user side, to keep the reporting of bug flow from breaking down, I suggest a
</I>>><i> two tier format that I discussed earlier. Maybe have a look at this and
</I>>><i> comment?
</I>>><i>
</I>>><i> I imagine that the Mageia devs are interested in hearing of bugs from as
</I>>><i> many sources as possible regardless of user experience.
</I>><i>
</I>><i> Here's the place where I may bring back to attention the proposed
</I>><i> system of helpers in the user forums. People who help unexperienced
</I>><i> users to write bug reports and will also help them along if the devs
</I>><i> ask questions during the lifetime of that bug in bugzilla. A user who
</I>><i> has done this once (ideally from the start of a bug until its end)
</I>><i> will be eager to do it again when he stumbles across another bug. He
</I>><i> will also be eager to "teach" his new knowledge to other users. This
</I>><i> way we will get a larger community of "bug reporters" than by any
</I>><i> documents.
</I>><i>
</I>><i> There must not be a fixed "Bug Friends" group, this "mentoring" can
</I>><i> be done by all experienced users.
</I>><i>
</I>
Actually, the process that you describe is exactly what mentoring is all
about. I would be in favour of both processes.
BTW ... someone mentioned that we should have a different thread for
this. Should we do this? Maybe call it "Report Bug Process" ?
Marc
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001264.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="001256.html">[Mageia-dev] Mageia repository sections, licenses, restrictions, firmware etc
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1275">[ date ]</a>
<a href="thread.html#1275">[ thread ]</a>
<a href="subject.html#1275">[ subject ]</a>
<a href="author.html#1275">[ 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>
|
