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
|
<!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=%3CPine.LNX.4.44.1010071649450.20026-100000%40outpost-priv%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="001002.html">
<LINK REL="Next" HREF="001007.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] How will be the realese cycle?</H1>
<B>Tux99</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=%3CPine.LNX.4.44.1010071649450.20026-100000%40outpost-priv%3E"
TITLE="[Mageia-dev] How will be the realese cycle?">tux99-mga at uridium.org
</A><BR>
<I>Thu Oct 7 16:58:42 CEST 2010</I>
<P><UL>
<LI>Previous message: <A HREF="001002.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="001007.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1003">[ date ]</a>
<a href="thread.html#1003">[ thread ]</a>
<a href="subject.html#1003">[ subject ]</a>
<a href="author.html#1003">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On Thu, 7 Oct 2010, nicolas vigier wrote:
><i> > It's the focus that changes, currently with Mandriva backports are a
</I>><i> > barely known unsupported afterthought.
</I>><i> > With a light rolling release scheme backports would be supported with
</I>><i> > regards to security fixes, since backports would be the preferred way to
</I>><i> > provide security fixes.
</I>><i> > It actually reduces workload since instead of the Mageia devs having to
</I>><i> > create themselves security patches for older releases, we just use the
</I>><i> > newer version of the sw from upstream that already includes the security
</I>><i> > patches.
</I>><i>
</I>><i> So what you're asking is basically to remove the updates repository
</I>><i> because you don't need it ?
</I>
The updates repo won't be removed since it's still needed for
security updates for the core distro packages, which won't be updated
to newer versions during a release cycle, only the apps that don't have
child dependencies (and where there are no major version changes with
incompatibilities).
><i> But what about the people who don't need new versions, but want stability
</I>><i> and security updates ?
</I>
As many people here have said already, version updates doesn't
automatically mean instability and/or incompatibilities, in fact such a
risk is very small, as anyone who has used backports in Mdv can confirm.
Someone who needs absolute stability (for example for important
servers), will always use other distros that specifically focus on that,
like Centos.
We cannot cater to everyone, I'm assuming that Mageia is primarily an
end-user desktop distro (like Mandriva was) so we might as well improve
it for that purpose.
If we try to cater for everyone we won't excell in anything, everything
will be compromises and the result will be mediocre.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="001002.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI>Next message: <A HREF="001007.html">[Mageia-dev] How will be the realese cycle?
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#1003">[ date ]</a>
<a href="thread.html#1003">[ thread ]</a>
<a href="subject.html#1003">[ subject ]</a>
<a href="author.html#1003">[ 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>
|
