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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] ANN: Recent changes in QA updates validation
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20ANN%3A%20Recent%20changes%20in%20QA%20updates%20validation&In-Reply-To=%3C201208151535.51192.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="018191.html">
<LINK REL="Next" HREF="018194.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] ANN: Recent changes in QA updates validation</H1>
<B>Samuel Verschelde</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20ANN%3A%20Recent%20changes%20in%20QA%20updates%20validation&In-Reply-To=%3C201208151535.51192.stormi%40laposte.net%3E"
TITLE="[Mageia-dev] ANN: Recent changes in QA updates validation">stormi at laposte.net
</A><BR>
<I>Wed Aug 15 15:35:51 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="018191.html">[Mageia-dev] The life After usrMove - KDE failure
</A></li>
<LI>Next message: <A HREF="018194.html">[Mageia-dev] Ruby update issues in cauldron
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18193">[ date ]</a>
<a href="thread.html#18193">[ thread ]</a>
<a href="subject.html#18193">[ subject ]</a>
<a href="author.html#18193">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hi,
During summer QA has not stopped working, and is still trying to improve the
process so that updates are pushed as quickly as possible.
First, the QA team now uses <A HREF="http://mageia.madb.org/tools/updates">http://mageia.madb.org/tools/updates</A> to have an
overview of current updates candidates. Major security updates are first in
list, in bold (or even red bold for highly critical ones). Those are usually
pushed very fast.
Other changes include :
--- Taking into account packager tests for updates they provided ---
Until now, packagers could not test their own updates. We decided to change
this rule because packagers often know their packages better than QA team. So
now packagers can test their own updates, within the following conditions:
only one arch per Mageia version, and final update validation must still be
done by a QA team member.
So when you provide an update, you can tell us what you have tested, on which
version and arch, and how (step by step instructions much appreciated!). Then
a QA team member will just have to test the other arch and validate the
update, hopefully very fast if a procedure is provided.
This policy change can be reviewed later if problems arise.
For the record, here is how QA tests update candidates:
<A HREF="https://wiki.mageia.org/en/QA_process_for_validating_updates#Test">https://wiki.mageia.org/en/QA_process_for_validating_updates#Test</A>
--- Identification of update candidates coming with a testing procedure ---
Update candidates that have a testing procedure (either provided by the
packager or by QA team members) are validated really faster than updates
candidates without a procedure. Indeed, most of QA's time is put in trying to
find how a package works, so we really appreciate testing instructions.
We added a new "has_procedure" whiteboard marker in bugzilla to identify
updates that have a testing procedure. They show in
<A HREF="http://mageia.madb.org/tools/updates">http://mageia.madb.org/tools/updates</A>
--- Identification of update candidates pending packager input ---
We added a new "feedback" whiteboard marker in bugzilla to identify updates
for which packager input has been requested. They have a gray background in
the aforementioned page.
Update candidates with that marker are held for a few days in hope that the
packager will answer (a simple "please push regardless of this issue" is
sometimes enough as a feedback), and QA members give priority to other updates
in the meantime.
Note : they are not held forever, unless the problem is found to be blocking.
We review stalled updates regularly, although we don't like pushing updates
when the packager doesn't answer our questions at al, of coursel. Critical
security fixes are usually not held this way. When questions are answered, QA
team usually removes the feedback marker itself, but don't hesitate to do so
yourself when answering!
Do you have any questions or remark?
Best regards
Samuel Verschelde
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="018191.html">[Mageia-dev] The life After usrMove - KDE failure
</A></li>
<LI>Next message: <A HREF="018194.html">[Mageia-dev] Ruby update issues in cauldron
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18193">[ date ]</a>
<a href="thread.html#18193">[ thread ]</a>
<a href="subject.html#18193">[ subject ]</a>
<a href="author.html#18193">[ 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>
|
