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] 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=%3CAANLkTim-ZL3_u9TkaG7CY%2B8VngxbvSFfFK%3DahsH%2B4NiX%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="000673.html">
<LINK REL="Next" HREF="000674.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] How will be the realese cycle?</H1>
<B>Ahmad Samir</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=%3CAANLkTim-ZL3_u9TkaG7CY%2B8VngxbvSFfFK%3DahsH%2B4NiX%40mail.gmail.com%3E"
TITLE="[Mageia-dev] How will be the realese cycle?">ahmadsamir3891 at gmail.com
</A><BR>
<I>Sat Oct 2 18:59:55 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="000673.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="000674.html">[Mageia-dev] About Mandriva tools future : Host Mandriva tools on github
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#679">[ date ]</a>
<a href="thread.html#679">[ thread ]</a>
<a href="subject.html#679">[ subject ]</a>
<a href="author.html#679">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 2 October 2010 14:50, Jérôme Martin <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at delaur.net</A>> wrote:
><i> Le vendredi 1 octobre 2010, Olivier Méjean a écrit :
</I>>><i> Le vendredi 1 octobre 2010 08:51:34, atilla ontas a écrit :
</I>><i>
</I>>><i> > What's your opinion?
</I>>><i>
</I>>><i> What about a rolling distribution ? As an user (just plain user) i do not
</I>>><i> think that installing a distribution is a goal, just a mean to use my
</I>>><i> computer, so i wish i could not spend time installing a distribution every
</I>>><i>  6 months or every year.
</I>>><i>
</I>><i>
</I>><i> My opinion is nearly the same: what is the need to provide a new version each
</I>><i> 6 months? The marketing point of view is not a valid answer since we do not
</I>><i> need to satsify shareholders or follow the market.
</I>><i>
</I>
Yes, but you have a distro to maintain, a reputation to uphold...
><i> So when a new version is needed? My point of view is that a new version is
</I>><i> needed when a big change will occur for exemple a new major release of KDE or
</I>><i> gnome, Xorg, perl, python, jdk, ...
</I>><i>
</I>><i> We need to change our view. Actually, the date of the release is decide and
</I>><i> the deciders (maketting, CEO, CTO, ?) choose which softwares will be include.
</I>><i> I propose to look at release date of the main softwares and decide when a new
</I>><i> version will be proposed.
</I>><i>
</I>
Hmm, no, IINM, that would be the release engineers job.
><i> For smaller software, we do not need to wait for a new version of the distro.
</I>><i> Just provide it as we do with the backport repository.
</I>
New version => new features + new bugs; anyone who ran cooker for a
good amount of time have witnessed this fact....
><i>
</I>><i> And no, rolling distro does mean use cauldron, since the system is not
</I>><i> supposed to work properly and where critical breakage can appear.
</I>><i>
</I>><i>
</I>
Ah, yes, so you want a rolling release, just like Cauldron will be,
but that's not broken; now how should one go about guaranteeing that
this will actually work out OK?
A rolling distro means double work for the devs and packagers as a new
version may just introduce new bugs too, now they don't provide the
new versions in a controlled development release where you're warned
that "this is a development release not suitable for day-to-day
production machines", or in a "unsupported backports" repo, no, it'll
just go to the stable release too.....
Now don't only think about a Mageia installation on a personal
computer, where even if the system is totally hosed you can easily do
a new install or restore a backup (then update to latest), but you
also have to bear in mind users who have servers doing all sorts of
jobs, they want stability over new-shiny-versions; the same goes for
school/university labs... etc.
--
Ahmad Samir
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000673.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="000674.html">[Mageia-dev] About Mandriva tools future : Host Mandriva tools on github
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#679">[ date ]</a>
<a href="thread.html#679">[ thread ]</a>
<a href="subject.html#679">[ subject ]</a>
<a href="author.html#679">[ 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>
|
