summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101001/000625.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101001/000625.html')
-rw-r--r--zarb-ml/mageia-dev/20101001/000625.html125
1 files changed, 125 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101001/000625.html b/zarb-ml/mageia-dev/20101001/000625.html
new file mode 100644
index 000000000..eaa31fcd1
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101001/000625.html
@@ -0,0 +1,125 @@
+<!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=%3C4CA63E41.2040907%40free.fr%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000641.html">
+ <LINK REL="Next" HREF="000640.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] How will be the realese cycle?</H1>
+ <B>Daniel Le Berre</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=%3C4CA63E41.2040907%40free.fr%3E"
+ TITLE="[Mageia-dev] How will be the realese cycle?">le.berred at free.fr
+ </A><BR>
+ <I>Fri Oct 1 22:02:09 CEST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000641.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI>Next message: <A HREF="000640.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#625">[ date ]</a>
+ <a href="thread.html#625">[ thread ]</a>
+ <a href="subject.html#625">[ subject ]</a>
+ <a href="author.html#625">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le 01/10/2010 20:03, Olivier M&#233;jean a &#233;crit :
+&gt;<i> Le vendredi 1 octobre 2010 08:51:34, atilla ontas a &#233;crit :
+</I>&gt;&gt;<i> I'm just wondering if we follow Mandriva's release cycle model. Every
+</I>&gt;&gt;<i> 6th months a release or one year and one release. I think we should
+</I>&gt;&gt;<i> make one release in one year. By doing so devs and translators won't
+</I>&gt;&gt;<i> be in rush in every 6 months. Also there are major changes like
+</I>&gt;&gt;<i> systemd/upstart; those system related things will be more mature in a
+</I>&gt;&gt;<i> year to use. It makes the distro more stable and decraese mirrors
+</I>&gt;&gt;<i> space waste.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> One more thing. Do we follow Mandriva's release naming scheme? I.e. do
+</I>&gt;&gt;<i> we call our first release 2011.x ? I don't like this naming scheme and
+</I>&gt;&gt;<i> suggesting using number of release as naming like Mageia 1.0 or using
+</I>&gt;&gt;<i> code names.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> What's your opinion?
+</I>&gt;&gt;<i>
+</I>&gt;<i>
+</I>&gt;<i> What about a rolling distribution ? As an user (just plain user) i do not
+</I>&gt;<i> think that installing a distribution is a goal, just a mean to use my
+</I>&gt;<i> computer, so i wish i could not spend time installing a distribution every 6
+</I>&gt;<i> months or every year.
+</I>&gt;<i>
+</I>&gt;<i>
+</I>
+Mandriva has allowed to properly upgrade an existing installation from
+the internet just if it was a normal security update for a few years (2
+at least).
+
+I do not see what would be the benefit of a rolling release compared to
+the current process.
+
+I am more concerned about the path from the cauldron to the final release.
+
+I do not know if it is possible, but I think that the way the Eclipse
+foundation is running the Eclipse project is worth mentioning:
+- they have milestone target every 6 weeks, aimed at power users (stable
+enough to run on their own, but might break compatibility with existing
+plugins).
+For a linux distribution, it would mean main elements ok, for contrib
+packages dependencies might be broken.
+- then they have a RC cycle in the last two months to produce the final
+release. Only major problems are fixed there, no new features.
+- Service releases are produced 3 months and 8 months after release, to
+integrate major bug fixes =&gt; this could be some xxxx.1 and xxxx.2
+releases after the main xxxx release.
+
+The main reason of the milestone is that Eclipse committers are more or
+less supposed to run the latest millestone: have your cake and eat it
+too. Any problem in the milestone should that way be met by those
+developers and quickly reported for a fix in the next milestone.
+
+Here the idea is that Mageia supporters willing to help making it better
+should be able to run the latest milestone without must risks
+(basic functionality working).
+
+All the details about Eclipse release process is available on:
+<A HREF="http://www.eclipse.org/projects/dev_process/development_process_2010.php">http://www.eclipse.org/projects/dev_process/development_process_2010.php</A>
+
+Daniel
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000641.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI>Next message: <A HREF="000640.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#625">[ date ]</a>
+ <a href="thread.html#625">[ thread ]</a>
+ <a href="subject.html#625">[ subject ]</a>
+ <a href="author.html#625">[ 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>