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 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=%3C1309102431.22020.339.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="006045.html">
<LINK REL="Next" HREF="005999.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=%3C1309102431.22020.339.camel%40akroma.ephaone.org%3E"
TITLE="[Mageia-dev] Backports policy proposal">misc at zarb.org
</A><BR>
<I>Sun Jun 26 17:33:50 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="006045.html">[Mageia-dev] Backports policy proposal
</A></li>
<LI>Next message: <A HREF="005999.html">[Mageia-dev] Backports policy proposal
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6047">[ date ]</a>
<a href="thread.html#6047">[ thread ]</a>
<a href="subject.html#6047">[ subject ]</a>
<a href="author.html#6047">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le dimanche 26 juin 2011 à 18:00 +0300, Anssi Hannula a écrit :
><i> On 26.06.2011 01:34, Michael Scherer wrote:
</I>><i> > Le vendredi 24 juin 2011 à 17:33 +0300, Anssi Hannula a écrit :
</I>><i> >> On 24.06.2011 03:10, Michael Scherer wrote:
</I>><i> >>> Another rule that we could add is that cauldron should always be newer
</I>><i> >>> than backports, in order to ensure upgradability. The same goes for n-2
</I>><i> >>> and n-1 release.
</I>><i> >>> While this seems innocent, do not forget this will have a impact when we
</I>><i> >>> do the version freeze.
</I>><i> >>
</I>><i> >> So this will prevent backporting anything to mga1 if it is not in mga2
</I>><i> >> release/updates ?
</I>><i> >
</I>><i> > That's a good question but yes, I would consider such policy.
</I>><i> > Ie, do backport only for the latest supported release.
</I>><i>
</I>><i> This will essentially prevent backporting anything to mga1 after mga2
</I>><i> release. :/
</I>
Yes, that's explicitly the problem.
Now, maybe we could say "if you use backports on version N after the
release of N+1, then mgaonline will no longer work". Provided we find a
user friendly way to warn users, we can maybe find something.
But again, it is either the backports or the upgrade. And people do have
expressed to have both :
- "reinstalling at every release is hard and annoying, why not do like
Ubuntu and Debian ?"
- "We want newer software, why not provides newer version ?"
So we either need a way to solve the dilemma, or at least, a way to
clearly explain the impact to people.
I think I may have a idea that would solve this issue and the one of
update, but I need to think a little bit before proposing it
( especially since I suffer from common cold, maybe my idea is
completely rubbish ).
--
Michael Scherer
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="006045.html">[Mageia-dev] Backports policy proposal
</A></li>
<LI>Next message: <A HREF="005999.html">[Mageia-dev] Backports policy proposal
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#6047">[ date ]</a>
<a href="thread.html#6047">[ thread ]</a>
<a href="subject.html#6047">[ subject ]</a>
<a href="author.html#6047">[ 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>
|
