blob: 2f128b3bcef9776bdf7d3a80e3bf80704d7d9778 (
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
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
|
<!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=%3C4EA02E7B.7080007%40arcor.de%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="009009.html">
<LINK REL="Next" HREF="009023.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Proposal for bug statuses and workflow</H1>
<B>Florian Hubold</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bug%20statuses%20and%20workflow&In-Reply-To=%3C4EA02E7B.7080007%40arcor.de%3E"
TITLE="[Mageia-dev] Proposal for bug statuses and workflow">doktor5000 at arcor.de
</A><BR>
<I>Thu Oct 20 16:21:47 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="009009.html">[Mageia-dev] Proposal for bug statuses and workflow
</A></li>
<LI>Next message: <A HREF="009023.html">[Mageia-dev] Proposal for bug statuses and workflow
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9014">[ date ]</a>
<a href="thread.html#9014">[ thread ]</a>
<a href="subject.html#9014">[ subject ]</a>
<a href="author.html#9014">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Am 19.10.2011 23:30, schrieb Samuel Verschelde:
><i> Here is a workflow proposal for bug reports in bugzilla.
</I>><i>
</I>><i> See the flowchart (link below) and the explanations below. Not all statuses
</I>><i> will be used in every bug report, but the flowchart more or less gives the
</I>><i> standard flow for bugs reported against a stable release of Mageia.
</I>><i>
</I>><i> <A HREF="http://stormi.lautre.net/fichiers/mageia/triage.png">http://stormi.lautre.net/fichiers/mageia/triage.png</A>
</I>><i>
</I>><i> NEW: as currently, bugs are set to this status when created
</I>><i>
</I>><i> NEW (+ NEEDINFO keyword): more input needed
</I>Why not set NEEDINFO keyword by default when a bug is reported and
a triager or the maintainer removes it then if sufficient information to work
on this bug is already present?
I'd say this being a keyword and not mandatory it will be forgotten often IMHO.
><i> NEW (+ Triaged keyword):
</I>><i>
</I>><i> ACCEPTED
</I>><i>
</I>><i> IN_PROGRESS
</I>really fine-grained but useless IMHO. If it has been triaged, there should be
someone
who works on that bug, and what reason would there be to not accept a bug?
Just my humble opinion. If those help to ease triage, why not.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="009009.html">[Mageia-dev] Proposal for bug statuses and workflow
</A></li>
<LI>Next message: <A HREF="009023.html">[Mageia-dev] Proposal for bug statuses and workflow
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9014">[ date ]</a>
<a href="thread.html#9014">[ thread ]</a>
<a href="subject.html#9014">[ subject ]</a>
<a href="author.html#9014">[ 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>
|