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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Updates testing
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Updates%20testing&In-Reply-To=%3C4E176DD3.4090807%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="006479.html">
<LINK REL="Next" HREF="006423.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Updates testing</H1>
<B>andre999</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Updates%20testing&In-Reply-To=%3C4E176DD3.4090807%40laposte.net%3E"
TITLE="[Mageia-dev] Updates testing">andr55 at laposte.net
</A><BR>
<I>Fri Jul 8 22:51:31 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006479.html">[Mageia-dev] Updates testing
</A></li>
<LI>Next message: <A HREF="006423.html">[Mageia-dev] [RPM] cauldron core/release gnome-control-center-3.1.3-1.mga2
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6490">[ date ]</a>
<a href="thread.html#6490">[ thread ]</a>
<a href="subject.html#6490">[ subject ]</a>
<a href="author.html#6490">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>philippe makowski a écrit :
><i> 2011/7/8 nicolas vigier<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">boklm at mars-attacks.org</A>>:
</I>>><i> I think the goal is not to do full regression tests, as we don't have
</I>>><i> time for this. But do minimal testing, in 1 or 2 minutes, to check that
</I>>><i> basic functionality is still working, to check that the update didn't
</I>>><i> break everything. For LibreOffice that could be opening a test document.
</I>>><i> Most applications are easy to test. But some require knowledge of the
</I>>><i> software, or some configuration files, to test, so we could keep a list
</I>>><i> of test commands or things to do and config files.
</I>><i> make sense
</I>
I agree
with a list of packages needing special consideration
><i> Fedora have interesting rules about update/testing updates
</I>><i>
</I>><i> Once pushed to testing, people are able to +1/-1 the updates "karma",
</I>><i> based on whether or not it seems to be functional for them. If your
</I>><i> update reaches a karma of 3, it will automatically be pushed to
</I>><i> stable. Likewise, if it reaches -3, it will be automatically unpushed.
</I>><i> If your update does not receive enough feedback to automatically push
</I>><i> it to stable, you will have to submit it as a final update yourself.
</I>><i> This can easily be done with the command-line tool, or with the web
</I>><i> interface
</I>
I like that approach, in general.
Although if it doesn't work for 1 user, but does for 4 others, it could end up
being pushed despite still having a bug.
(Likely if the bug depends on other apps installed, affecting only a subset of
users.)
><i> they also have "proven tester"
</I>><i> <A HREF="https://fedoraproject.org/wiki/Proven_tester">https://fedoraproject.org/wiki/Proven_tester</A> for critical path package
</I>
--
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006479.html">[Mageia-dev] Updates testing
</A></li>
<LI>Next message: <A HREF="006423.html">[Mageia-dev] [RPM] cauldron core/release gnome-control-center-3.1.3-1.mga2
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6490">[ date ]</a>
<a href="thread.html#6490">[ thread ]</a>
<a href="subject.html#6490">[ subject ]</a>
<a href="author.html#6490">[ 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>
|
