diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-November/009454.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-November/009454.html | 124 |
1 files changed, 124 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-November/009454.html b/zarb-ml/mageia-dev/2011-November/009454.html new file mode 100644 index 000000000..a06ff03f0 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-November/009454.html @@ -0,0 +1,124 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20%5BRPM%5D%20cauldron%20core/release%0A%09kdenlive-0.8.2-1.mga2&In-Reply-To=%3C201111092339.51308.anaselli%40linux.it%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="009445.html"> + <LINK REL="Next" HREF="009529.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2</H1> + <B>Angelo Naselli</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20%5BRPM%5D%20cauldron%20core/release%0A%09kdenlive-0.8.2-1.mga2&In-Reply-To=%3C201111092339.51308.anaselli%40linux.it%3E" + TITLE="[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2">anaselli at linux.it + </A><BR> + <I>Wed Nov 9 23:39:46 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="009445.html">[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2 +</A></li> + <LI>Next message: <A HREF="009529.html">[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9454">[ date ]</a> + <a href="thread.html#9454">[ thread ]</a> + <a href="subject.html#9454">[ subject ]</a> + <a href="author.html#9454">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> +><i> If shit happen, then 151 bugs is IMHO a rather serious diarrhea. +</I>Ok i get your point here. + +><i> > The point is not why we released, but why not to update it. +</I>><i> +</I>><i> My point is "why do we do the work twice". +</I>Because developers are not perfect and even if they do their best +they always make mistakes (to avoid any war, me first). +Let's have a look at gnome bugzilla and check our mga 1 evolution: +<A HREF="http://tinyurl.com/dyydha9">http://tinyurl.com/dyydha9</A> +Then our kmail: +<A HREF="http://tinyurl.com/crwo8wp">http://tinyurl.com/crwo8wp</A> +So if we look at those tables we should avoid to ship them to prevent +any update or trust them and eventually fix something, following their +develop or their releases. In any case now they are in (and maybe a crash +can make our mails to be lost)... + +Thanks God we avoid kmail2 but i seem to recall it was in for a while... +maybe mikala was so good to avoid to have it in mga1, i'm not very happy +using it in cauldron(not to say mdv 2011)... maybe i won't in mga2... +or maybe upstream team fixes a lot of bugs before... +but that could be an mga2 story :) + +><i> In case people didn't notice, there was a thread about "there is too +</I>><i> much update". Some stuff are unavoidable, like security updates. +</I>but they ask also ISOSs with updates to dowload once.... +Anyway we could also quote people that in past asked for updates that never +came. + +><i> Some others could be avoided. And shipping a update is more costly ( it +</I>><i> involve more people and a more complex process ) than shiping a proper +</I>><i> package in the first place. +</I>That requires more test in cauldron... bug you know well that end-user bugs +come not before betas for the most.... + +><i> So the best way to ensure less updates is to find why we do need to +</I>><i> update in the first place. IE, how could have we prevented it. +</I>i don't think less updates is right anyway, i think we should update in a +right manner... which means more tests, more answers from reporters +and hopefully a good cover test -and yes it costs-. + +><i> And if we were not able to detect regression in the first place, how can +</I>><i> we make sure that the update will fix something ? +</I>I agree it's not always easy, but i take this thread to tell a problem i'm +looking these days, hplip and more probably ghostscript packages, +in mga1 i can't print photos -they are printed darker using a lot of ink-, +is it blocking? Maybe no, but it is for me -and my purse- and for other people +that reported it -one is using mandriva 2010.1 for that only-. +Now I'm studying how to fix it (it works in cauldron now), but i know already +that i cannot upgrade ghostscript and hplip, so great... the problem is solved +then. +I mean if someone, like me, spends his time to fix some but can't do an update +that is time lost, and what's worst the bug still stays opened... +Is that good? +I think we should always consider case by case, but also the story a potencial +update had... + + +-- + Angelo +-------------- next part -------------- +A non-text attachment was scrubbed... +Name: not available +Type: application/pgp-signature +Size: 198 bytes +Desc: This is a digitally signed message part. +URL: </pipermail/mageia-dev/attachments/20111109/8ede312e/attachment.asc> +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="009445.html">[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2 +</A></li> + <LI>Next message: <A HREF="009529.html">[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9454">[ date ]</a> + <a href="thread.html#9454">[ thread ]</a> + <a href="subject.html#9454">[ subject ]</a> + <a href="author.html#9454">[ 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> |