summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-November/009544.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-November/009544.html')
-rw-r--r--zarb-ml/mageia-dev/2011-November/009544.html99
1 files changed, 99 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-November/009544.html b/zarb-ml/mageia-dev/2011-November/009544.html
new file mode 100644
index 000000000..dd5cde93b
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-November/009544.html
@@ -0,0 +1,99 @@
+<!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=%3C201111150935.31004.stormi%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="009542.html">
+ <LINK REL="Next" HREF="009553.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2</H1>
+ <B>Samuel Verschelde</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=%3C201111150935.31004.stormi%40laposte.net%3E"
+ TITLE="[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2">stormi at laposte.net
+ </A><BR>
+ <I>Tue Nov 15 09:35:30 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="009542.html">[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2
+</A></li>
+ <LI>Next message: <A HREF="009553.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#9544">[ date ]</a>
+ <a href="thread.html#9544">[ thread ]</a>
+ <a href="subject.html#9544">[ subject ]</a>
+ <a href="author.html#9544">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le mardi 15 novembre 2011 07:40:13, Michael Scherer a &#233;crit :
+&gt;<i> Le lundi 14 novembre 2011 &#224; 19:29 -0300, Balcaen John a &#233;crit :
+</I>&gt;<i> &gt; Le lundi 14 novembre 2011 23:17:32 zezinho a &#233;crit :
+</I>&gt;<i> &gt; &gt; Le lundi 14 novembre 2011 20:23:40, Juan Luis Baptiste a &#233;crit :
+</I>&gt;<i> &gt; &gt; &gt; So what is the final decision about this ? is there going to be an
+</I>&gt;<i> &gt; &gt; &gt; update or not ?
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; I vote no, let's wait for backports, like all other new versions.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; i not agree at all because
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; - we did it for KDE SC 4.6 (upgrading from 4.6.3 to 4.6.5).
+</I>&gt;<i> &gt; - the list of bug fixes (especially the number of crash &amp; corruption
+</I>&gt;<i> &gt; fix) - it's a *minor* version not a major one
+</I>&gt;<i>
+</I>&gt;<i> The policy is not about minor version, it is bugfixes only. Not
+</I>&gt;<i> everybody make the distinction between minor and major, especially for
+</I>&gt;<i> software developpers.
+</I>&gt;<i>
+</I>&gt;<i> And again, the question of QA is here. Since we didn't detect the
+</I>&gt;<i> regression ( and since there is so much crashes to fix, and sine
+</I>&gt;<i> everybody think that's important enough to bypass our policy, according
+</I>&gt;<i> to people in the thread ), how do people plan to make sure the most
+</I>&gt;<i> obvious one are corrected ?
+</I>&gt;<i>
+</I>&gt;<i> Do we have open bug reports about them, with clear reproducer ?
+</I>&gt;<i>
+</I>&gt;<i> And do at least someone plan to use kdenlive enough to say &quot;this fixed
+</I>&gt;<i> the bug I have been seeing before&quot; ?
+</I>&gt;<i>
+</I>&gt;<i> Or do we plan to do &quot;it started, so it is good enough, let's ship it&quot; ?
+</I>
+Of course QA will test more than &quot;the program started, it's OK&quot;. If you look
+at the history of updates in bugzilla you'll see that testing is usually more
+thorough than that.
+
+And if the packager asks for testing of new features to ensure they introduce
+no obvious blocking bug, they can be tested, provided they are in a limited
+number. If that's the price for dozens of bugfixes, it can be worth it, unless
+the new features are disruptive for users accustomed to the version of
+kdenlive in core/release, or bring incompatibilities or new critical bugs.
+
+Samuel
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="009542.html">[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2
+</A></li>
+ <LI>Next message: <A HREF="009553.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#9544">[ date ]</a>
+ <a href="thread.html#9544">[ thread ]</a>
+ <a href="subject.html#9544">[ subject ]</a>
+ <a href="author.html#9544">[ 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>