diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005704.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005704.html | 108 |
1 files changed, 108 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005704.html b/zarb-ml/mageia-dev/2011-June/005704.html new file mode 100644 index 000000000..5ed8982a3 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005704.html @@ -0,0 +1,108 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Finalizing update process + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Finalizing%20update%20process&In-Reply-To=%3C4DF8A398.1070706%40mageia.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005702.html"> + <LINK REL="Next" HREF="005707.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Finalizing update process</H1> + <B>Thomas Backlund</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Finalizing%20update%20process&In-Reply-To=%3C4DF8A398.1070706%40mageia.org%3E" + TITLE="[Mageia-dev] Finalizing update process">tmb at mageia.org + </A><BR> + <I>Wed Jun 15 14:20:40 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005702.html">[Mageia-dev] Finalizing update process +</A></li> + <LI>Next message: <A HREF="005707.html">[Mageia-dev] Finalizing update process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5704">[ date ]</a> + <a href="thread.html#5704">[ thread ]</a> + <a href="subject.html#5704">[ subject ]</a> + <a href="author.html#5704">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Michael Scherer skrev 15.6.2011 15:10: +><i> Le mercredi 15 juin 2011 à 07:55 -0400, Stew Benedict a écrit : +</I>>><i> On 06/12/2011 08:25 AM, Angelo Naselli wrote: +</I>>>><i> In data mercoledì 8 giugno 2011 23:53:51, Ahmad Samir ha scritto: +</I>>>>>>><i> Right, I probably phrased that one wrongly; I meant: +</I>>>>>>><i> fixes a serious bug, e.g. crashing, segfaulting +</I>>>>>><i> I don't think we should exclude non-serious bugs :) +</I>>>>><i> Depends, overworking the sec team doesn't look like a good aspect... +</I>>>>><i> (that's why I liked contrib in mdv, I could push an update any time, +</I>>>>><i> without having to go though the bug report -> QA -> Sec team loop). +</I>>>><i> Well here we could stop at QA team step, or at least someone more that can +</I>>>><i> test and say that the fixing is good... +</I>>>><i> +</I>>><i> So, +</I>>><i> +</I>>><i> We've had a lot of discussion, which is good, but imho we need to start +</I>>><i> getting some updates out the door. Users are asking for them and the +</I>>><i> CVEs just keep rolling in. +</I>>><i> +</I>>><i> As I understand it, the mechanics are in place to issue updates, and +</I>>><i> I've put together a page as a first pass at a policy, based on my memory +</I>>><i> of how things worked in the past and what I've picked up from the +</I>>><i> discussion. +</I>>><i> +</I>>><i> <A HREF="http://mageia.org/wiki/doku.php?id=updates_policy">http://mageia.org/wiki/doku.php?id=updates_policy</A> +</I>>><i> +</I>>><i> Randomly, I'm targeting 2 bugs to push through, to test the process: +</I>>><i> +</I>>><i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=1084">https://bugs.mageia.org/show_bug.cgi?id=1084</A> (vde2, app crashes) +</I>>><i> <A HREF="https://bugs.mageia.org/show_bug.cgi?id=1521">https://bugs.mageia.org/show_bug.cgi?id=1521</A> (subversion, security issue) +</I>>><i> +</I>>><i> Now, first problem is we still don't have a maintainer database, so who +</I>>><i> gets the assignment, the person that first imported the package? +</I>>><i> Perhaps this is the first change to the policy - maintainer or any +</I>>><i> interested packager initiates the update +</I>><i> +</I>><i> Sound sensible, yes. +</I>><i> +</I>><i> The idea IMHO is not to prevent people for doing the work if they wish, +</I>><i> but if there is no volunteer, it should be the duty of someone, and this +</I>><i> someone is the maintainer. +</I>><i> Now, we do not have a official maintainer db, but the test instance is +</I>><i> still here afaik. So yes, picking someone from the list of person that +</I>><i> committed would do the trick. +</I>><i> +</I> +BTW, should we have a read-only security/update-announce ml that where +we mail about all updates ? + +-- +Thomas + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005702.html">[Mageia-dev] Finalizing update process +</A></li> + <LI>Next message: <A HREF="005707.html">[Mageia-dev] Finalizing update process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5704">[ date ]</a> + <a href="thread.html#5704">[ thread ]</a> + <a href="subject.html#5704">[ subject ]</a> + <a href="author.html#5704">[ 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> |