diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101007/000931.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101007/000931.html | 190 |
1 files changed, 190 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101007/000931.html b/zarb-ml/mageia-dev/20101007/000931.html new file mode 100644 index 000000000..b9da8fd4a --- /dev/null +++ b/zarb-ml/mageia-dev/20101007/000931.html @@ -0,0 +1,190 @@ +<!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=%3C4CAD133F.20900%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000945.html"> + <LINK REL="Next" HREF="000935.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How will be the realese cycle?</H1> + <B>andré</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=%3C4CAD133F.20900%40laposte.net%3E" + TITLE="[Mageia-dev] How will be the realese cycle?">andr55 at laposte.net + </A><BR> + <I>Thu Oct 7 02:24:31 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="000945.html">[Mageia-dev] A new office suite ? +</A></li> + <LI>Next message: <A HREF="000935.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#931">[ date ]</a> + <a href="thread.html#931">[ thread ]</a> + <a href="subject.html#931">[ subject ]</a> + <a href="author.html#931">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Ahmad Samir a écrit : +><i> 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>><i> +</I>>><i> Le vendredi 1 octobre 2010, Olivier Méjean a écrit : +</I>>><i> +</I>>>><i> Le vendredi 1 octobre 2010 08:51:34, atilla ontas a écrit : +</I>>>><i> +</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>Just because there is a new version of the distro every 6 months doesn't +mean you have to install it. It just means that there is a truely +stable version every 6 months. Some users will want to upgrade every 6 +months, and some every 2 years (or whatever the maximum support +period). Many may prefer to wait 3 months after release to ensure that +the minor bugs remaining are found. +In the meantime, just use the upgrade functions -- Mandriva, which we +will presumably follow initially allows upgrading for any/all of +security-correctives, other-bug-correctives, general-upgrades, and +backports. + +The advantage of a new version of Mageia every 6 months is that it is a +collection of software that works well (except for inevitable minor +bugs) with versions that work together. Some users, like myself, prefer +to upgrade every 6 months. +Also, new users would prefer to start with a relatively recent stable +version. +Creating a stable version every 6 months is a lot easier than a rolling +distro, or much shorter periods. +Note that individual applications not infrequently encounter major bugs +in a presumably stable version. For a distro, creating frequent stable +versions would be much more problematic. +The down side of stable versions every 6 months is somewhat less recent +software, but those who want more recent can always download a backport. +>><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> Yes, but you have a distro to maintain, a reputation to uphold... +</I>><i> +</I>Very important +>><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>This would not be workable. Even though many applications do produce +major releases about every 6 months, they rarely coincide. As well as +often being delayed due to unexpected bugs. Do we really want a new +release every few months ? +It is much more useful for a major distribution (as hopefully Mageia +becomes) to have releases at more or less predictable intervals. +>><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>><i> Hmm, no, IINM, that would be the release engineers job. +</I>><i> +</I>><i> +</I>>><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>>><i> +</I>><i> New version => new features + new bugs; anyone who ran cooker for a +</I>><i> good amount of time have witnessed this fact.... +</I>><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> Ah, yes, so you want a rolling release, just like Cauldron will be, +</I>><i> but that's not broken; now how should one go about guaranteeing that +</I>><i> this will actually work out OK? +</I>><i> +</I>><i> A rolling distro means double work for the devs and packagers as a new +</I>><i> version may just introduce new bugs too, now they don't provide the +</I>><i> new versions in a controlled development release where you're warned +</I>><i> that "this is a development release not suitable for day-to-day +</I>><i> production machines", or in a "unsupported backports" repo, no, it'll +</I>><i> just go to the stable release too..... +</I>><i> +</I>I would say a lot more than double the work. And more than double the +resources. +><i> Now don't only think about a Mageia installation on a personal +</I>><i> computer, where even if the system is totally hosed you can easily do +</I>><i> a new install or restore a backup (then update to latest), but you +</I>><i> also have to bear in mind users who have servers doing all sorts of +</I>><i> jobs, they want stability over new-shiny-versions; the same goes for +</I>><i> school/university labs... etc. +</I>><i> +</I>And even for personal use, not many would appreciate having to do an +unanticipated reinstall or restore from backup. Particularly those who +want to avoid upgrading their distro every 6 months. ;) + +Rolling distro, anyone ? + +- André (andre999) +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000945.html">[Mageia-dev] A new office suite ? +</A></li> + <LI>Next message: <A HREF="000935.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#931">[ date ]</a> + <a href="thread.html#931">[ thread ]</a> + <a href="subject.html#931">[ subject ]</a> + <a href="author.html#931">[ 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> |