summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101005/000836.html
blob: 34361284c12bab33b5049e7e20a5b4310fafa3a6 (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
<!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=%3C236.4cab27fe%40mageia.linuxtech.net%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="000829.html">
   <LINK REL="Next"  HREF="000838.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=%3C236.4cab27fe%40mageia.linuxtech.net%3E"
       TITLE="[Mageia-dev] How will be the realese cycle?">tux99-mga at uridium.org
       </A><BR>
    <I>Tue Oct  5 15:28:31 CEST 2010</I>
    <P><UL>
        <LI>Previous message: <A HREF="000829.html">[Mageia-dev] [Mageia-discuss] About Mandriva tools future : Host Mandriva tools on github
</A></li>
        <LI>Next message: <A HREF="000838.html">[Mageia-dev] How will be the realese cycle?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#836">[ date ]</a>
              <a href="thread.html#836">[ thread ]</a>
              <a href="subject.html#836">[ subject ]</a>
              <a href="author.html#836">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>

Personally I think the way Mandriva maintains both updates and backports
for each release is a waste of resources.

I do agree that Mageia should be a semi-rolling distro.

By &quot;semi rolling distro&quot; I mean the following:

Release a distro every 8-12 months (the exact cyle is not the point I'm
debating here, it could be 6 months too, it doesn't mater for the concept
I'm trying to explain).

Provide updates/security patches for all the basic stuff that has a lot of
dependencies (kernel, core libs, kde, gnome, xorg, etc.).

Provide newer release rather than backported security patches for all other
apps.

In other words, backports (rather than backported security fixes) should be
the rule for everything apart from the core system stuff that has loads of
dependencies.

This would reduce the space requirements on the mirrors and it would mean
that Mageia is a &quot;rolling distro&quot; for most apps, making it more attractive
compared to ubuntu/Fedora/opensuse and at the same time reduce the workload
for packagers.

</PRE>








<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="000829.html">[Mageia-dev] [Mageia-discuss] About Mandriva tools future : Host Mandriva tools on github
</A></li>
	<LI>Next message: <A HREF="000838.html">[Mageia-dev] How will be the realese cycle?
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#836">[ date ]</a>
              <a href="thread.html#836">[ thread ]</a>
              <a href="subject.html#836">[ subject ]</a>
              <a href="author.html#836">[ 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>