zarb-ml/mageia-dev/2011-June/006045.html


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Backports policy proposal
   </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%20proposal&In-Reply-To=%3C4E074976.5000504%40iki.fi%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="006019.html">
   <LINK REL="Next"  HREF="006047.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Backports policy proposal</H1>
    <B>Anssi Hannula</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20proposal&In-Reply-To=%3C4E074976.5000504%40iki.fi%3E"
       TITLE="[Mageia-dev] Backports policy proposal">anssi.hannula at iki.fi
       </A><BR>
    <I>Sun Jun 26 17:00:06 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="006019.html">[Mageia-dev] Backports policy proposal
</A></li>
        <LI>Next message: <A HREF="006047.html">[Mageia-dev] Backports policy proposal
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6045">[ date ]</a>
              <a href="thread.html#6045">[ thread ]</a>
              <a href="subject.html#6045">[ subject ]</a>
              <a href="author.html#6045">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On 26.06.2011 01:34, Michael Scherer wrote:
&gt;<i> Le vendredi 24 juin 2011 &#224; 17:33 +0300, Anssi Hannula a &#233;crit :
</I>&gt;&gt;<i> On 24.06.2011 03:10, Michael Scherer wrote:
</I>&gt;&gt;&gt;<i> Another rule that we could add is that cauldron should always be newer
</I>&gt;&gt;&gt;<i> than backports, in order to ensure upgradability. The same goes for n-2
</I>&gt;&gt;&gt;<i> and n-1 release.
</I>&gt;&gt;&gt;<i> While this seems innocent, do not forget this will have a impact when we
</I>&gt;&gt;&gt;<i> do the version freeze.
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> So this will prevent backporting anything to mga1 if it is not in mga2
</I>&gt;&gt;<i> release/updates ?
</I>&gt;<i> 
</I>&gt;<i> That's a good question but yes, I would consider such policy.
</I>&gt;<i> Ie, do backport only for the latest supported release.
</I>
This will essentially prevent backporting anything to mga1 after mga2
release. :/

-- 
Anssi Hannula
</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="006019.html">[Mageia-dev] Backports policy proposal
</A></li>
	<LI>Next message: <A HREF="006047.html">[Mageia-dev] Backports policy proposal
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#6045">[ date ]</a>
              <a href="thread.html#6045">[ thread ]</a>
              <a href="subject.html#6045">[ subject ]</a>
              <a href="author.html#6045">[ 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>