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
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Proposal for bug statuses and workflow
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bug%20statuses%20and%20workflow&In-Reply-To=%3C201110192330.05856.stormi%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="009081.html">
<LINK REL="Next" HREF="008997.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Proposal for bug statuses and workflow</H1>
<B>Samuel Verschelde</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bug%20statuses%20and%20workflow&In-Reply-To=%3C201110192330.05856.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] Proposal for bug statuses and workflow">stormi at laposte.net
</A><BR>
<I>Wed Oct 19 23:30:05 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="009081.html">[Mageia-dev] require help to understand stage1/stage2/rescue source files
</A></li>
<LI>Next message: <A HREF="008997.html">[Mageia-dev] Proposal for bug statuses and workflow
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8995">[ date ]</a>
<a href="thread.html#8995">[ thread ]</a>
<a href="subject.html#8995">[ subject ]</a>
<a href="author.html#8995">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Here is a workflow proposal for bug reports in bugzilla.
See the flowchart (link below) and the explanations below. Not all statuses
will be used in every bug report, but the flowchart more or less gives the
standard flow for bugs reported against a stable release of Mageia.
<A HREF="http://stormi.lautre.net/fichiers/mageia/triage.png">http://stormi.lautre.net/fichiers/mageia/triage.png</A>
NEW: as currently, bugs are set to this status when created
NEW (+ NEEDINFO keyword): more input needed
NEW (+ Triaged keyword): bug report has been triaged by a triager or
maintainer, and should have been assigned to the right maintainer (when
there's one), but there's no guarantee about this.
ACCEPTED must be set by the maintainer, or a packager who decides to fix the
bug for the maintainer. It doesn't mean that the packager is actively working
on the fix, but shows that he/she is willing to whenever possible. Setting a
bug report to accepted acknowledges that the triager assigned to the right
person AND that this person saw that the bug report was assigned to him/her.
In case of a bug assigned to a maintainer group (when there will be), setting
the status to ACCEPTED means that the group is OK to handle the bug report,
but it does not mean that someone from the group is already working on it. See
the next status for that.
IN_PROGRESS can be set by the packager who is working on the bug. It is not
mandatory, this status can be skipped. However, it is advised to use it to
give better feedback to both triagers and bug reporters.
TESTING is set when assigning to QA Team (ideally bugzilla would automatically
assign to QA when someone puts the TESTING status in a stable release).
VALIDATED is set by QA team once testing ends. It means that the update can be
pushed (replaces the validated_update keyword)
CLOSED replaces RESOLVED, because I think it's nicer for the bug reporter if
we "close" bugs rather than consider them "resolved" when the reason for
closing is WONT-FIX, DUPLICATE, OLD, etc., statuses that obviously don't match
the meaning of "RESOLVED".
ASSIGNED status disappears, because it was ambiguous. UNCONFIRMED disappears,
it was unused already.
Here are the proposed Resolutions:
FIXED
NOT_A_BUG (replaces INVALID with a more neutral term)
INSUFFICIENT_DATA (new resolution for bugs closed due to lack of data)
CANT_FIX (it's too difficult to fix it, or there's a reason why we can't fix it)
WONT_FIX (we don't *want* to fix it)
DUPLICATE
WORKS_FOR_ME
Best regards
Samuel Verschelde
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="009081.html">[Mageia-dev] require help to understand stage1/stage2/rescue source files
</A></li>
<LI>Next message: <A HREF="008997.html">[Mageia-dev] Proposal for bug statuses and workflow
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8995">[ date ]</a>
<a href="thread.html#8995">[ thread ]</a>
<a href="subject.html#8995">[ subject ]</a>
<a href="author.html#8995">[ 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>
|
