summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005983.html
blob: a555de4737489f4781d1aa18c55d77c5741e6667 (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
118
119
<!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=%3C1308908673.22020.177.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="005981.html">
   <LINK REL="Next"  HREF="005994.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Backports policy proposal</H1>
    <B>Michael Scherer</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20proposal&In-Reply-To=%3C1308908673.22020.177.camel%40akroma.ephaone.org%3E"
       TITLE="[Mageia-dev] Backports policy proposal">misc at zarb.org
       </A><BR>
    <I>Fri Jun 24 11:44:32 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="005981.html">[Mageia-dev] Backports policy proposal
</A></li>
        <LI>Next message: <A HREF="005994.html">[Mageia-dev] Backports policy proposal
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#5983">[ date ]</a>
              <a href="thread.html#5983">[ thread ]</a>
              <a href="subject.html#5983">[ subject ]</a>
              <a href="author.html#5983">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Le vendredi 24 juin 2011 &#224; 08:30 +0200, Maarten Vanraes a &#233;crit :
&gt;<i> Op vrijdag 24 juni 2011 02:10:14 schreef Michael Scherer:
</I>&gt;<i> [...]
</I>&gt;<i> &gt; Another rule that we could add is that cauldron should always be newer
</I>&gt;<i> &gt; than backports, in order to ensure upgradability. The same goes for n-2
</I>&gt;<i> &gt; and n-1 release.
</I>&gt;<i> &gt; While this seems innocent, do not forget this will have a impact when we
</I>&gt;<i> &gt; do the version freeze.
</I>&gt;<i> [..]
</I>&gt;<i> 
</I>&gt;<i> This seems hard to enforce... i can imagine if you make backport, it has 
</I>&gt;<i> essentially the same version as in cauldron, i can think that there is a few 
</I>&gt;<i> spec file changes that are only for backports, and thus the release becomes 
</I>&gt;<i> newer than the one in cauldron
</I>
Youri has a module for that ( recency I think ), and we used this in
PLF.

And if there is changes that would make sense just for backport, one can
play with release tag to be older, or can just rebuild in cauldron to be
newer before backporting.
-- 
Michael Scherer

</PRE>









































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