summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-January/011253.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-January/011253.html')
-rw-r--r--zarb-ml/mageia-dev/2012-January/011253.html153
1 files changed, 153 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-January/011253.html b/zarb-ml/mageia-dev/2012-January/011253.html
new file mode 100644
index 000000000..65d57bb8a
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-January/011253.html
@@ -0,0 +1,153 @@
+<!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=%3CCAPZ-hqSimGrQtU6JPJVvAiuky1ULJjrSthnwmpKMzyFfAvP-MA%40mail.gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="011244.html">
+ <LINK REL="Next" HREF="011271.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1</H1>
+ <B>Juan Luis Baptiste</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=%3CCAPZ-hqSimGrQtU6JPJVvAiuky1ULJjrSthnwmpKMzyFfAvP-MA%40mail.gmail.com%3E"
+ TITLE="[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1">juancho at mageia.org
+ </A><BR>
+ <I>Wed Jan 11 21:10:01 CET 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="011244.html">[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1
+</A></li>
+ <LI>Next message: <A HREF="011271.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#11253">[ date ]</a>
+ <a href="thread.html#11253">[ thread ]</a>
+ <a href="subject.html#11253">[ subject ]</a>
+ <a href="author.html#11253">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>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:
+&gt;<i> Le mercredi 11 janvier 2012 &#224; 11:24 -0500, Juan Luis Baptiste a &#233;crit :
+</I>&gt;<i>
+</I>&gt;<i> So trusting and having bugs are totally unrelated. And if you doubt that
+</I>&gt;<i> bugs appear, just see our bugzilla.
+</I>&gt;<i> We trust upstream ( most of them ), and yet there is bugs.
+</I>
+No, they're not totally unrelated when we don't have the man power to
+do through QA on every package, we need to trust on the packager (and
+upstream of course) that he did his best to test the new version
+without expecting him to have tested all the new features, Or do you
+expect that a QA member get a list of all the new features of a
+backport and start testing them one by one ? that's what I call
+unrealistic in practice.
+
+&gt;<i>
+</I>&gt;&gt;<i> If you think that all version backports should be tested in the same
+</I>&gt;&gt;<i> way as updates by QA, then all versions upgrades in cauldron should be
+</I>&gt;&gt;<i> tested by QA before pushing them to the BS right ?
+</I>&gt;<i>
+</I>&gt;<i> No, they should be tested before being put in the stable release. And
+</I>&gt;<i> that's exactly what we do by freezing and testing before release.
+</I>&gt;<i>
+</I>
+Of course but again, we can't test *all* the new features of *all* the
+programs that are going to a new release, we do our best for most of
+them. Critical components like installer, kernel, drak* tools, etc
+need more testing and that's where (our very small team) QA should
+spend their time after a freeze. The rest we have to do our best to
+test after each version update of a package.
+
+&gt;&gt;<i> why risk for a bug
+</I>&gt;&gt;<i> on a program when updating to a new mga version and not when doing a
+</I>&gt;&gt;<i> backport ?, it's exactly the same situation.
+</I>&gt;<i>
+</I>&gt;<i> That was already extensively discussed in the past, but if we do the
+</I>&gt;<i> same stuff than in Mandriva, we will end with the same result than in
+</I>&gt;<i> Mandriva.
+</I>&gt;<i> - people don't test backports, because that's not mandatory
+</I>&gt;<i> =&gt; some bugs slips.
+</I>&gt;<i>
+</I>
+Of course and that will also happen when updating packages during the
+development cycle of cauldron. Yes, we do freeze to be able to test,
+but we cant test every new feature of all applications. We test the
+most critical stuff which we can't risk to have bugs (and they also
+slip some times).
+
+&gt;<i>
+</I>&gt;<i> In the end, users complain that distribution is broken, and that impact
+</I>&gt;<i> our image. We cannot tell &quot;do not mix&quot;, because we cannot tell them to
+</I>&gt;<i> update backports without fear, as that would be lying. And in the end,
+</I>&gt;<i> saying &quot;this is not supported, but we offer to you&quot; is just sending a
+</I>&gt;<i> confusing message.
+</I>&gt;<i>
+</I>&gt;<i> If we start to give low quality stuff as Mageia, people will just think
+</I>&gt;<i> Mageia is low quality.
+</I>&gt;<i>
+</I>
+Users will complain anyway, they will complain because there aren't
+backports of their favorite application or because a backported
+version has a bug, so we need to find a balance between those two.
+Expecting to do the same amount of testing to a backport will put too
+much burden on QA and will make the process of backporting a version
+too slow for the users. So we need to have more lax tests for
+backports, enough to guarantee that the application works for it's
+main features and doesn't put too much burnden on QA, than for updates
+which need to gurantee that a bug is really fixed. How to define which
+should be those tests ? that's the issue as I see it. We could have a
+&quot;backports team&quot; thought, that would do QA for backports without
+taking time from the updates QA team...
+
+Also the other problem is the third-party repos which brings lots of
+problems because packages are of low quality and don't follow our
+standards, and if we don't have our own backports and move fast enough
+users will continue to use those third-party repos, which will also
+bring the &quot;Mageia is of low quality&quot; problem.
+
+
+--
+Juancho
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="011244.html">[Mageia-dev] please stop doing &quot;bugs&quot; for updating magia 1
+</A></li>
+ <LI>Next message: <A HREF="011271.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#11253">[ date ]</a>
+ <a href="thread.html#11253">[ thread ]</a>
+ <a href="subject.html#11253">[ subject ]</a>
+ <a href="author.html#11253">[ 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>