blob: 556cb6be9a0641575a0849840fd4ea7e757e45b8 (
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
|
<!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=%3CBANLkTin%2BVcxx%3D_rFyXApcxuxbyK06in82Q%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="004713.html">
<LINK REL="Next" HREF="004719.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Security Update Process</H1>
<B>Thierry Vignaud</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Security%20Update%20Process&In-Reply-To=%3CBANLkTin%2BVcxx%3D_rFyXApcxuxbyK06in82Q%40mail.gmail.com%3E"
TITLE="[Mageia-dev] Security Update Process">thierry.vignaud at gmail.com
</A><BR>
<I>Mon May 16 18:08:59 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="004713.html">[Mageia-dev] Security Update Process
</A></li>
<LI>Next message: <A HREF="004719.html">[Mageia-dev] Security Update Process
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4714">[ date ]</a>
<a href="thread.html#4714">[ thread ]</a>
<a href="subject.html#4714">[ subject ]</a>
<a href="author.html#4714">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>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> 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>
What's more that matches what we were doing back @mdv.
The process was:
- trusted packagers upload into main/testing,
- all packager can upload into contrib/testing,
- ticket (for main/*) is opened & assigned to qa
- people || qa test
- if tests succeed, ticket is assigned to secteam
- secteam rebuild with its own sig & push the package
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="004713.html">[Mageia-dev] Security Update Process
</A></li>
<LI>Next message: <A HREF="004719.html">[Mageia-dev] Security Update Process
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#4714">[ date ]</a>
<a href="thread.html#4714">[ thread ]</a>
<a href="subject.html#4714">[ subject ]</a>
<a href="author.html#4714">[ 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>
|
