summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20110518/004746.html
blob: 067b3f0ec785d5475bf2c368385c03bb234b24a7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
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 &#224; 18:08 +0200, Thierry Vignaud a &#233;crit :
&gt;<i> On 16 May 2011 18:05, Ahmad Samir &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>&gt; wrote:
</I>&gt;<i> &gt;&gt;&gt; Mageia 1 is approaching quickly and we need to get our process in place
</I>&gt;<i> &gt;&gt;&gt; for security updates. We talked a bit about it a few weeks ago, and I
</I>&gt;<i> &gt;&gt;&gt; started a wiki page, but it needs more detail. Anne and I chatted on IRC
</I>&gt;<i> &gt;&gt;&gt; and it looks like we'll want to cutoff the &quot;on the iso &quot; updates at the
</I>&gt;<i> &gt;&gt;&gt; end of this week, so we need a process in place to release post-iso updates.
</I>&gt;<i> &gt;&gt;&gt;
</I>&gt;<i> &gt;&gt;&gt; ref: <A HREF="http://mageia.org/wiki/doku.php?id=security">http://mageia.org/wiki/doku.php?id=security</A>
</I>&gt;<i> &gt;&gt;&gt;
</I>&gt;<i> &gt;&gt;&gt; As I see it, initially we need, in no particular order:
</I>&gt;<i> &gt;&gt;&gt;
</I>&gt;<i> &gt;&gt;&gt; 1) a means to build updates for the release (iurt setup for mga1?)
</I>&gt;<i> &gt;&gt;
</I>&gt;<i> &gt;&gt; A iurt setup for mga1 will exist anyway, what is missing is a way to
</I>&gt;<i> &gt;&gt; later upload to non public place.
</I>&gt;<i> &gt;&gt; Initially, we can just setup youri to restrict submitting a build to
</I>&gt;<i> &gt;&gt; updates_testing or updates to the secteam and it should be enough.
</I>&gt;<i> &gt;&gt;
</I>&gt;<i> &gt;
</I>&gt;<i> &gt; Ideally packagers should be able to submit to update_testing when they
</I>&gt;<i> &gt; want to push a fixed package to ask for testing. So restricting
</I>&gt;<i> &gt; submitting to updates sounds more logical?
</I>&gt;<i> 
</I>&gt;<i> What's more that matches what we were doing back @mdv.
</I>&gt;<i> The process was:
</I>&gt;<i> - trusted packagers upload into main/testing,
</I>&gt;<i> - all packager can upload into contrib/testing,
</I>&gt;<i> - ticket (for main/*) is opened &amp; assigned to qa
</I>&gt;<i> - people || qa test
</I>&gt;<i> - if tests succeed, ticket is assigned to secteam
</I>&gt;<i> - secteam rebuild with its own sig &amp; 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>