summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-January/011271.html
blob: 6dbb0c81909491642e03665072ca33b2aabc8467 (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
111
112
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20please%20stop%20doing%20%22bugs%22%20for%20updating%20magia%201&In-Reply-To=%3C201201121048.41289.bgmilne%40zarb.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="011253.html">
   <LINK REL="Next"  HREF="011283.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1</H1>
    <B>Buchan Milne</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20please%20stop%20doing%20%22bugs%22%20for%20updating%20magia%201&In-Reply-To=%3C201201121048.41289.bgmilne%40zarb.org%3E"
       TITLE="[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1">bgmilne at zarb.org
       </A><BR>
    <I>Thu Jan 12 09:48:40 CET 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="011253.html">[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1
</A></li>
        <LI>Next message: <A HREF="011283.html">[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#11271">[ date ]</a>
              <a href="thread.html#11271">[ thread ]</a>
              <a href="subject.html#11271">[ subject ]</a>
              <a href="author.html#11271">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On Wednesday, 11 January 2012 22:10:01 Juan Luis Baptiste wrote:
&gt;<i> On Wed, Jan 11, 2012 at 2:10 PM, Michael Scherer &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>&gt; wrote:
</I>&gt;<i> &gt; Le mercredi 11 janvier 2012 &#224; 11:24 -0500, Juan Luis Baptiste a &#233;crit :
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; So trusting and having bugs are totally unrelated. And if you doubt that
</I>&gt;<i> &gt; bugs appear, just see our bugzilla.
</I>&gt;<i> &gt; We trust upstream ( most of them ), and yet there is bugs.
</I>&gt;<i> 
</I>&gt;<i> No, they're not totally unrelated when we don't have the man power to
</I>&gt;<i> do through QA on every package, we need to trust on the packager (and
</I>&gt;<i> upstream of course) that he did his best to test the new version
</I>&gt;<i> without expecting him to have tested all the new features, Or do you
</I>&gt;<i> expect that a QA member get a list of all the new features of a
</I>&gt;<i> backport and start testing them one by one ? that's what I call
</I>&gt;<i> unrealistic in practice.
</I>&gt;<i> 
</I>&gt;<i> &gt;&gt; If you think that all version backports should be tested in the same
</I>&gt;<i> &gt;&gt; way as updates by QA, then all versions upgrades in cauldron should be
</I>&gt;<i> &gt;&gt; tested by QA before pushing them to the BS right ?
</I>&gt;<i> &gt; 
</I>&gt;<i> &gt; No, they should be tested before being put in the stable release. And
</I>&gt;<i> &gt; that's exactly what we do by freezing and testing before release.
</I>&gt;<i> 
</I>&gt;<i> Of course but again, we can't test *all* the new features of *all* the
</I>&gt;<i> programs that are going to a new release, we do our best for most of
</I>&gt;<i> them. Critical components like installer, kernel, drak* tools, etc
</I>&gt;<i> need more testing and that's where (our very small team) QA should
</I>&gt;<i> spend their time after a freeze. The rest we have to do our best to
</I>&gt;<i> test after each version update of a package.
</I>
And this is IMHO why we should not necessarily enforce full QA on backports.

It is ridiculous to enforce more testing on a package in backports, than most 
likely was done for it while in cauldron before a release, especially 
considering the user has a relatively easy mechanism for reverting to the 
working package.

If QA can state definitively that every package in a release is fully tested, 
then I might agree.

But, some of the reason to *have* backports is to allow users on stable 
releases to test new versions that exist in cauldron.

Regards,
Buchan
</PRE>













<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="011253.html">[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1
</A></li>
	<LI>Next message: <A HREF="011283.html">[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#11271">[ date ]</a>
              <a href="thread.html#11271">[ thread ]</a>
              <a href="subject.html#11271">[ subject ]</a>
              <a href="author.html#11271">[ 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>