summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005704.html
blob: 5ed8982a3be5ddee61237435546fa059b25ae052 (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
102
103
104
105
106
107
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:
&gt;<i> Le mercredi 15 juin 2011 &#224; 07:55 -0400, Stew Benedict a &#233;crit :
</I>&gt;&gt;<i> On 06/12/2011 08:25 AM, Angelo Naselli wrote:
</I>&gt;&gt;&gt;<i> In data mercoled&#236; 8 giugno 2011 23:53:51, Ahmad Samir ha scritto:
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> Right, I probably phrased that one wrongly; I meant:
</I>&gt;&gt;&gt;&gt;&gt;&gt;<i> fixes a serious bug, e.g. crashing, segfaulting
</I>&gt;&gt;&gt;&gt;&gt;<i> I don't think we should exclude non-serious bugs :)
</I>&gt;&gt;&gt;&gt;<i> Depends, overworking the sec team doesn't look like a good aspect...
</I>&gt;&gt;&gt;&gt;<i> (that's why I liked contrib in mdv, I could push an update any time,
</I>&gt;&gt;&gt;&gt;<i> without having to go though the bug report -&gt;   QA -&gt;   Sec team loop).
</I>&gt;&gt;&gt;<i> Well here we could stop at QA team step, or at least someone more that can
</I>&gt;&gt;&gt;<i> test  and say that the fixing is good...
</I>&gt;&gt;&gt;<i>
</I>&gt;&gt;<i> So,
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> We've had a lot of discussion, which is good, but imho we need to start
</I>&gt;&gt;<i> getting some updates out the door. Users are asking for them and the
</I>&gt;&gt;<i> CVEs just keep rolling in.
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> As I understand it, the mechanics are in place to issue updates, and
</I>&gt;&gt;<i> I've put together a page as a first pass at a policy, based on my memory
</I>&gt;&gt;<i> of how things worked in the past and what I've picked up from the
</I>&gt;&gt;<i> discussion.
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> <A HREF="http://mageia.org/wiki/doku.php?id=updates_policy">http://mageia.org/wiki/doku.php?id=updates_policy</A>
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> Randomly, I'm targeting 2 bugs to push through, to test the process:
</I>&gt;&gt;<i>
</I>&gt;&gt;<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>&gt;&gt;<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>&gt;&gt;<i>
</I>&gt;&gt;<i> Now, first problem is we still don't have a maintainer database, so who
</I>&gt;&gt;<i> gets the assignment, the person that first imported the package?
</I>&gt;&gt;<i> Perhaps this is the first change to the policy - maintainer or any
</I>&gt;&gt;<i> interested packager initiates the update
</I>&gt;<i>
</I>&gt;<i> Sound sensible, yes.
</I>&gt;<i>
</I>&gt;<i> The idea IMHO is not to prevent people for doing the work if they wish,
</I>&gt;<i> but if there is no volunteer, it should be the duty of someone, and this
</I>&gt;<i> someone is the maintainer.
</I>&gt;<i> Now, we do not have a official maintainer db, but the test instance is
</I>&gt;<i> still here afaik. So yes, picking someone from the list of person that
</I>&gt;<i> committed would do the trick.
</I>&gt;<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>