summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-November/009554.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-November/009554.html')
-rw-r--r--zarb-ml/mageia-dev/2011-November/009554.html141
1 files changed, 141 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-November/009554.html b/zarb-ml/mageia-dev/2011-November/009554.html
new file mode 100644
index 000000000..bb70d4c90
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-November/009554.html
@@ -0,0 +1,141 @@
+<!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=%3C33903549.xFCl0A0F82%40hatmehyt-cauldron.lan.littleboboy.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="009580.html">
+ <LINK REL="Next" HREF="009568.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2</H1>
+ <B>Balcaen John</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=%3C33903549.xFCl0A0F82%40hatmehyt-cauldron.lan.littleboboy.net%3E"
+ TITLE="[Mageia-dev] [changelog] [RPM] cauldron core/release kdenlive-0.8.2-1.mga2">mikala at mageia.org
+ </A><BR>
+ <I>Tue Nov 15 12:13:48 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="009580.html">[Mageia-dev] BuildRequires and pkgconfig
+</A></li>
+ <LI>Next message: <A HREF="009568.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#9554">[ date ]</a>
+ <a href="thread.html#9554">[ thread ]</a>
+ <a href="subject.html#9554">[ subject ]</a>
+ <a href="author.html#9554">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le mardi 15 novembre 2011 07:40:13 Michael Scherer a &#233;crit :
+[...]
+&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>Well to be honest i can't be sure that a minor version of KDE is *reallly* bug
+fixes only, even if it's wrote like this upstream.
+&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>Did we have from the start the minimum of people able to use &amp; came in the
+situation of trigger them ?
+
+
+&gt;<i> Do we have open bug reports about them, with clear reproducer ?
+</I>The answer here depends of above.
+But the question about having bug reports about them with *clear* reproducer
+is interresting.
+Let's take an example :
+
+If an end user found a bug/crash in kdeenlive he might be not able to provide
+a clear way to reproduce it because he's using some specific codecs with
+specific options and so he might be able to provide only the backtrace.
+Sometimes upstream can directly fix the crash using this backtrace because it's
+obvious (from a coder point of view of course , not from my point of view :p
+), so the end user will be happy.
+What should we do in that case ? backport the patch for a crash where we don't
+have any reproducer to ensure our QA is able to test &amp; report it fixed ? or
+just ignore it because of our policy ?
+because of course fixing this bug could introduce another one etc etc.
+
+Perhaps some users of kdenlive of mageia noticed some of thoses
+crash/corruption but did not report them on mageia's bugzilla because
+- they don't know how to do it or not able to provide a &#171; clear &#187; way to
+reproduce it
+- they report directly upstream
+
+Sticking to a have a clear reproducer to get a patch available in our package
+might reduce the chance of passing the QA :)
+
+
+&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>I'm not sure we have enough users to ensure that some of them will report the
+bug on our bugzilla, not to mention the fact that some users still see the
+bugzilla as a write only media...
+
+
+&gt;<i> Or do we plan to do &quot;it started, so it is good enough, let's ship it&quot; ?
+</I>Here's the packager is supposed to provides a list of things to test &amp; not let
+QA alone.
+Regarding kdeenlive for example every issue listed on the changelog is linked
+to their bugzilla so the packager (poor juancho :p ) might be able to provide
+a list of things to test.
+
+Also we should not forget that our process for backports is the same so QA
+will need to do the same work (that's also why i personnaly won't backport
+anything to ease the work for our small QA) so the idea of pushing kdenlive to
+backports instead of updates does not solve the situation from a QA
+perspective.
+
+Anyway since it's our policy i'll stick strictly on it now to avoid this kind
+of situation (&amp; next time i'll try to follow with more attention our work on
+policy :p). I'll try also to manager sometimes to take part of the QA process
+to increase the number of people available in this team.
+
+
+Regards,
+
+--
+Balcaen John
+Jabber-id: <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mikala at jabber.littleboboy.net</A>
+</PRE>
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="009580.html">[Mageia-dev] BuildRequires and pkgconfig
+</A></li>
+ <LI>Next message: <A HREF="009568.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#9554">[ date ]</a>
+ <a href="thread.html#9554">[ thread ]</a>
+ <a href="subject.html#9554">[ subject ]</a>
+ <a href="author.html#9554">[ 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>