diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/20110518/004746.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/20110518/004746.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20110518/004746.html | 101 |
1 files changed, 101 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20110518/004746.html b/zarb-ml/mageia-dev/20110518/004746.html new file mode 100644 index 000000000..067b3f0ec --- /dev/null +++ b/zarb-ml/mageia-dev/20110518/004746.html @@ -0,0 +1,101 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Security 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%20Security%20Update%20Process&In-Reply-To=%3C1305751225.3709.2.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="004744.html"> + <LINK REL="Next" HREF="004745.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Security Update Process</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Security%20Update%20Process&In-Reply-To=%3C1305751225.3709.2.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] Security Update Process">misc at zarb.org + </A><BR> + <I>Wed May 18 22:37:14 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="004744.html">[Mageia-dev] Freeze push request: mysql +</A></li> + <LI>Next message: <A HREF="004745.html">[Mageia-dev] Security Update Process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#4746">[ date ]</a> + <a href="thread.html#4746">[ thread ]</a> + <a href="subject.html#4746">[ subject ]</a> + <a href="author.html#4746">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le lundi 16 mai 2011 à 18:08 +0200, Thierry Vignaud a écrit : +><i> On 16 May 2011 18:05, Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> wrote: +</I>><i> >>> Mageia 1 is approaching quickly and we need to get our process in place +</I>><i> >>> for security updates. We talked a bit about it a few weeks ago, and I +</I>><i> >>> started a wiki page, but it needs more detail. Anne and I chatted on IRC +</I>><i> >>> and it looks like we'll want to cutoff the "on the iso " updates at the +</I>><i> >>> end of this week, so we need a process in place to release post-iso updates. +</I>><i> >>> +</I>><i> >>> ref: <A HREF="http://mageia.org/wiki/doku.php?id=security">http://mageia.org/wiki/doku.php?id=security</A> +</I>><i> >>> +</I>><i> >>> As I see it, initially we need, in no particular order: +</I>><i> >>> +</I>><i> >>> 1) a means to build updates for the release (iurt setup for mga1?) +</I>><i> >> +</I>><i> >> A iurt setup for mga1 will exist anyway, what is missing is a way to +</I>><i> >> later upload to non public place. +</I>><i> >> Initially, we can just setup youri to restrict submitting a build to +</I>><i> >> updates_testing or updates to the secteam and it should be enough. +</I>><i> >> +</I>><i> > +</I>><i> > Ideally packagers should be able to submit to update_testing when they +</I>><i> > want to push a fixed package to ask for testing. So restricting +</I>><i> > submitting to updates sounds more logical? +</I>><i> +</I>><i> What's more that matches what we were doing back @mdv. +</I>><i> The process was: +</I>><i> - trusted packagers upload into main/testing, +</I>><i> - all packager can upload into contrib/testing, +</I>><i> - ticket (for main/*) is opened & assigned to qa +</I>><i> - people || qa test +</I>><i> - if tests succeed, ticket is assigned to secteam +</I>><i> - secteam rebuild with its own sig & push the package +</I> +I would propose the following : +- packagers can upload to */updates_testing ( with some limitation and +specific check ) +- ticket are opened for everything, assigned to QA +- people || qa test +- if tests are ok, package is moved to */updates + +I see no need to rebuild again on a different system, as we do not have +the ressources. + +-- +Michael Scherer + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="004744.html">[Mageia-dev] Freeze push request: mysql +</A></li> + <LI>Next message: <A HREF="004745.html">[Mageia-dev] Security Update Process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#4746">[ date ]</a> + <a href="thread.html#4746">[ thread ]</a> + <a href="subject.html#4746">[ subject ]</a> + <a href="author.html#4746">[ 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> |