diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-July/017181.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-July/017181.html | 118 |
1 files changed, 118 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-July/017181.html b/zarb-ml/mageia-dev/2012-July/017181.html new file mode 100644 index 000000000..7818011b6 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-July/017181.html @@ -0,0 +1,118 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Security%20updates%20-%20Help%20needed%20%28also%0A%09forgot%09avidemux%20and%20gstreamer0.10-ffmpeg%29&In-Reply-To=%3C20120705215100.GL21938%40mars-attacks.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="017227.html"> + <LINK REL="Next" HREF="017182.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg)</H1> + <B>nicolas vigier</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Security%20updates%20-%20Help%20needed%20%28also%0A%09forgot%09avidemux%20and%20gstreamer0.10-ffmpeg%29&In-Reply-To=%3C20120705215100.GL21938%40mars-attacks.org%3E" + TITLE="[Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg)">boklm at mars-attacks.org + </A><BR> + <I>Thu Jul 5 23:51:00 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="017227.html">[Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg) +</A></li> + <LI>Next message: <A HREF="017182.html">[Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#17181">[ date ]</a> + <a href="thread.html#17181">[ thread ]</a> + <a href="subject.html#17181">[ subject ]</a> + <a href="author.html#17181">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Thu, 05 Jul 2012, Guillaume Rousse wrote: + +><i> Le 04/07/2012 01:21, David Walser a écrit : +</I>>><i> Sorry, think I've got them all now. +</I>>><i> +</I>>><i> For avidemux and gstreamer0.10-ffmpeg in Mageia 1, it may be sufficient to borrow the patches from the mplayer update. +</I>>><i> +</I>>><i> For avidemux in Mageia 2, patches will need to be pulled from ffmpeg GIT. +</I>>><i> +</I>>><i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=6427">https://bugs.mageia.org/show_bug.cgi?id=6427</A> +</I>><i> I spent some time today to help the QA team to manage those pending +</I>><i> security updates. And for the second time in a week, I've been facing +</I>><i> rather unpleasant attitude from someone else from the same team: +</I>><i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=5939">https://bugs.mageia.org/show_bug.cgi?id=5939</A> +</I>><i> +</I>><i> I wonder how we're supposed to work together when expressing an opinion +</I>><i> about issues prioritization expose you to harsh comment from someone unable +</I>><i> to express his disagreement without agressivity. That's not much point +</I>><i> ressorting to "we're all in the same boat" kind of metaphor during IRC +</I>><i> meeting to thereafter suggest to leave the board to people expressing +</I>><i> concerns about the boat heading... +</I>><i> +</I>><i> So, before any further contribution from my side, I'd like the people in +</I>><i> charge of security updates to find some internal agreement about what kind +</I>><i> of help they expect from other people exactly. If that's just to push a +</I>><i> non-discussable list of changes into spec files, they could as well ask for +</I>><i> SVN commit and package submission rights, to do it directly. This would +</I>><i> avoid a large amount of anger and frustration for everyone. +</I> +About prioritization, I think we should remember that : +- we want security updates quickly, to reduce the time users will have + vulnerable systems +- we don't want regressions in updates, that's why we need QA team to test + the updates, and why we avoid major changes in updates +- all people working on Mageia are volunteers, have limited time and + probably other external constraints. We can ask them to make an effort + when there is an urgency, but this should not be abused. + +So I think it would make sense to have a policy that say that when a +bug that is not a regression is found while testing an update, it can +be mentioned for information, but it should not block the validation of +the update. Packager can fix it while fixing the other issue, if he has +time, but he doesn't fix it if he is too busy or think it introduce too +much changes for an update. In that case the issue can be fixed later +when the packager has some free time, with no hurry. + +</PRE> + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="017227.html">[Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg) +</A></li> + <LI>Next message: <A HREF="017182.html">[Mageia-dev] Security updates - Help needed (also forgot avidemux and gstreamer0.10-ffmpeg) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#17181">[ date ]</a> + <a href="thread.html#17181">[ thread ]</a> + <a href="subject.html#17181">[ subject ]</a> + <a href="author.html#17181">[ 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> |