blob: e8385919eba8bb146e702664a07a04db42e1db48 (
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
109
110
111
112
113
114
115
116
117
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Backports policy clarification (and discussion)
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3C201206081331.30983.anaselli%40linux.it%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016271.html">
<LINK REL="Next" HREF="016281.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Backports policy clarification (and discussion)</H1>
<B>Angelo Naselli</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3C201206081331.30983.anaselli%40linux.it%3E"
TITLE="[Mageia-dev] Backports policy clarification (and discussion)">anaselli at linux.it
</A><BR>
<I>Fri Jun 8 13:31:30 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016271.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI>Next message: <A HREF="016281.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16278">[ date ]</a>
<a href="thread.html#16278">[ thread ]</a>
<a href="subject.html#16278">[ subject ]</a>
<a href="author.html#16278">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>
><i> If there is security issue then you have to fix it on cauldron too (usually with new
</I>><i> version, so you can backport it to stable version). At least before release. And after
</I>><i> backports are closed you can upgrade to latest stable version (for example mga3) and get
</I>><i> patched version this way. I don't see the problem here.
</I>Well I can't see how we can close a bp since we say we give 9 months of supporting version.
If we support bp, we also need to provides fixing at least. But i got your point, it's
a kind o release freeze for bp for the mga n-2.
Angelo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/mageia-dev/attachments/20120608/f739e328/attachment.asc>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016271.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI>Next message: <A HREF="016281.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16278">[ date ]</a>
<a href="thread.html#16278">[ thread ]</a>
<a href="subject.html#16278">[ subject ]</a>
<a href="author.html#16278">[ 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>
|
