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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] How will be the realese cycle?
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C201010021034.24306.omejean%40yahoo.fr%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000646.html">
<LINK REL="Next" HREF="000662.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] How will be the realese cycle?</H1>
<B>Olivier Méjean</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C201010021034.24306.omejean%40yahoo.fr%3E"
TITLE="[Mageia-dev] How will be the realese cycle?">omejean at yahoo.fr
</A><BR>
<I>Sat Oct 2 10:34:23 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000646.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="000662.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#660">[ date ]</a>
<a href="thread.html#660">[ thread ]</a>
<a href="subject.html#660">[ subject ]</a>
<a href="author.html#660">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Le samedi 2 octobre 2010 02:09:47, nicolas vigier a écrit :
><i>
</I>><i> This rolling release already exists, it's called the backport
</I>><i> repository. But don't expect the same stability as the fixed release,
</I>><i> you can't have both.
</I>><i>
</I>
Well, i disagree for a good reason, in free software there is no (or mainly
no) separation between new versions of a software only correcting bugs, and
new versions of the same software adding new functionnalities. Let's take an
example, digikam.
Changes from digikam 1.3 to 1.4 are bugs correction affecting digikam 1.3 and
addition of new functionnalities. So what ? I need digikam more stable so
let's use the version that corrects bugs, so the latest, but it also adds new
functionnalities that may provide bugs ... (and in the case of Digikam 1.4 it
requires KDE 4.5, unfortunately there is no update to KDE 4.5 for Mandriva
2010 !) what to do ?
I also add that creating backports is creating new packages for older versions
that is more time to compilation, more time to ensure quality, and so. In the
whole i am not sure that it.
There are exceptions for development, such as Scribus which delivers two
versions :
- 1.3.3.x (current and last version 1.3.3.14) which has been improved over
time by bug correction (no addition of new functionnalities)
-1.3.6, 1.3.7, 1.3.8 and 1.3.9 which are development version, adding new
functionnalities, bugs correction.
You just have to go on sourceforge to see how Scribus works :
<A HREF="http://sourceforge.net/projects/scribus/files/">http://sourceforge.net/projects/scribus/files/</A> there is a stable version
1.3.3.14, devel versions and svn versions. Devel are quite stable, usable but
Scribus team still have them as devel versions and recommend that distribution
package 2 scribus versions : scribus package for the stable version 1.3.3.14
and scribus-ng for development package, this is not the case for Mandriva, it
had causes some problem when i was doing Magnum since some of us were using
1.3.3.x branch others with more recent were using 1.3.6 devel branch creating
incompatibilites between files.
So one cannot say that stability is affected by backport when backported
packages are to correct existing bugs (but maybe adding new bugs due to new
functionnalities). Noboby would say that KDE 4.1 is more stable than KDE 4.5
but there is no means to update KDE 4.x to KDE 4.x+1 at the moment, and i
consider that must be in update policies. With Mandriva 2010 i am stick to
4.3.5 and i bet there will be no more evolution for KDE 4.3 branch.
--
Olivier Méjean
Président de l'Association des Utilisateurs Francophones de Mandriva Linux
<A HREF="http://mandrivafr.org">http://mandrivafr.org</A>
twitter : obagoom
identi.ca : goom
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000646.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="000662.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#660">[ date ]</a>
<a href="thread.html#660">[ thread ]</a>
<a href="subject.html#660">[ subject ]</a>
<a href="author.html#660">[ 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>
|
