diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-January/011244.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-January/011244.html | 135 |
1 files changed, 135 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-January/011244.html b/zarb-ml/mageia-dev/2012-January/011244.html new file mode 100644 index 000000000..99542ccd1 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/011244.html @@ -0,0 +1,135 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] please stop doing "bugs" 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=%3C1326309002.19749.21.camel%40liliana.cdg.redhat.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="011236.html"> + <LINK REL="Next" HREF="011253.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] please stop doing "bugs" for updating magia 1</H1> + <B>Michael Scherer</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=%3C1326309002.19749.21.camel%40liliana.cdg.redhat.com%3E" + TITLE="[Mageia-dev] please stop doing "bugs" for updating magia 1">misc at zarb.org + </A><BR> + <I>Wed Jan 11 20:10:02 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="011236.html">[Mageia-dev] please stop doing "bugs" for updating magia 1 +</A></li> + <LI>Next message: <A HREF="011253.html">[Mageia-dev] please stop doing "bugs" for updating magia 1 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#11244">[ date ]</a> + <a href="thread.html#11244">[ thread ]</a> + <a href="subject.html#11244">[ subject ]</a> + <a href="author.html#11244">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le mercredi 11 janvier 2012 à 11:24 -0500, Juan Luis Baptiste a écrit : +><i> On Wed, Jan 11, 2012 at 3:43 AM, Florian Hubold <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">doktor5000 at arcor.de</A>> wrote: +</I>><i> > Well, 2) and 3) are not valid reasons here, because backports should get +</I>><i> > a similar amount of QA testing as normal update candidates, and for +</I>><i> > the updates policy require a bugreport for validation through QA. +</I>><i> +</I>><i> I think this is unrealistic in practice. For updates, QA will be +</I>><i> testing one bug fix, with a backport you will have dozens or more new +</I>><i> features to test, you can't expect for QA to test all of them to be +</I>><i> able to give the OK, more if they even don't use the backported app in +</I>><i> a daily basis. Testing of a backport has to be more relaxed and +</I>><i> compromise to test some basic stuff like that it installs and starts +</I>><i> correctly, maybe the package maintainer can give some hints on what +</I>><i> else to test, but the rest we will have to trust in the maintainer's +</I>><i> judgement. +</I> +So trusting and having bugs are totally unrelated. And if you doubt that +bugs appear, just see our bugzilla. +We trust upstream ( most of them ), and yet there is bugs. + +><i> If you think that all version backports should be tested in the same +</I>><i> way as updates by QA, then all versions upgrades in cauldron should be +</I>><i> tested by QA before pushing them to the BS right ? +</I> +No, they should be tested before being put in the stable release. And +that's exactly what we do by freezing and testing before release. + +><i> why risk for a bug +</I>><i> on a program when updating to a new mga version and not when doing a +</I>><i> backport ?, it's exactly the same situation. +</I> +That was already extensively discussed in the past, but if we do the +same stuff than in Mandriva, we will end with the same result than in +Mandriva. +- people don't test backports, because that's not mandatory +=> some bugs slips. + +then users start to say "do not use backport if you do not know what you +do or if you are not expert, because I had $problem once". With time, +such advice start to impermeate the community, and people start to +simply not use backports. + +Worst, some people just do cherry picking of backports, and take one or +two or them, and this result in wierd bugs with 2 effects : +- we lose time +- user think we are doing a bad quality distribution, because he has a +mix that he is the only one in the world to have. Non technical users +tell him he should not mix ( and they are right ), and so he start to +feel bad because we gave him something that do not ork. Some users also +end with system unsupported, so no security update, nor bugfixes. + +In the end, users complain that distribution is broken, and that impact +our image. We cannot tell "do not mix", because we cannot tell them to +update backports without fear, as that would be lying. And in the end, +saying "this is not supported, but we offer to you" is just sending a +confusing message. + +If we start to give low quality stuff as Mageia, people will just think +Mageia is low quality. + +-- +Michael Scherer + +</PRE> + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="011236.html">[Mageia-dev] please stop doing "bugs" for updating magia 1 +</A></li> + <LI>Next message: <A HREF="011253.html">[Mageia-dev] please stop doing "bugs" for updating magia 1 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#11244">[ date ]</a> + <a href="thread.html#11244">[ thread ]</a> + <a href="subject.html#11244">[ subject ]</a> + <a href="author.html#11244">[ 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> |