From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/20101006/000912.html | 80 +++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 zarb-ml/mageia-dev/20101006/000912.html (limited to 'zarb-ml/mageia-dev/20101006/000912.html') diff --git a/zarb-ml/mageia-dev/20101006/000912.html b/zarb-ml/mageia-dev/20101006/000912.html new file mode 100644 index 000000000..d036f34c5 --- /dev/null +++ b/zarb-ml/mageia-dev/20101006/000912.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] How will be the realese cycle? + + + + + + + + + +

[Mageia-dev] How will be the realese cycle?

+ Cassian Braconnnier + ptyxs at free.fr +
+ Wed Oct 6 20:50:00 CEST 2010 +

+
+ +
Le 06/10/2010 20:31, Michael Scherer a écrit :
+> Le mercredi 06 octobre 2010 à 14:55 -0300, Gustavo Giampaoli a écrit :
+>    
+>>>> So a one year release cycle with lots of app backports (and maybe a kernel
+>>>> backport mid-cycle if there is important new hardware support) is IMHO the
+>>>> best release cycle for 'normal' users.
+>>>>          
+>> Just take a look to Windows XP users. Almost 10 years of bugfixes and
+>> patches almost without any mayor change in the OS. But XP is still on
+>> the road. And it's because you can have the latest software "and"
+>> hardware in your ten years old OS.
+>>
+>> I'm not saying that Mageia should last ten years. But IMHO that "XP
+>> case" is a valid example.
+>>      
+> Sure, when we will have the money of Microsoft, and the team they have
+> for QA, I am sure we will be able to do it too...
+Precisely for that latter reason a fork was not a good idea, in my 
+opinion : better fuse, merge, unite with other distros than create new 
+little projects...
+(sorry, I am going out immediately...)
+
+
+
+
+
+ + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1