summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005576.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005576.html')
-rw-r--r--zarb-ml/mageia-dev/2011-June/005576.html180
1 files changed, 180 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005576.html b/zarb-ml/mageia-dev/2011-June/005576.html
new file mode 100644
index 000000000..7c5681572
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-June/005576.html
@@ -0,0 +1,180 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Release cycles proposals, and discussion
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycles%20proposals%2C%20and%20discussion&In-Reply-To=%3C201106140330.56794.maarten.vanraes%40gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="005567.html">
+ <LINK REL="Next" HREF="005577.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Release cycles proposals, and discussion</H1>
+ <B>Maarten Vanraes</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycles%20proposals%2C%20and%20discussion&In-Reply-To=%3C201106140330.56794.maarten.vanraes%40gmail.com%3E"
+ TITLE="[Mageia-dev] Release cycles proposals, and discussion">maarten.vanraes at gmail.com
+ </A><BR>
+ <I>Tue Jun 14 03:30:56 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="005567.html">[Mageia-dev] Release cycles proposals, and discussion
+</A></li>
+ <LI>Next message: <A HREF="005577.html">[Mageia-dev] Release cycles proposals, and discussion
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5576">[ date ]</a>
+ <a href="thread.html#5576">[ thread ]</a>
+ <a href="subject.html#5576">[ subject ]</a>
+ <a href="author.html#5576">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Op dinsdag 14 juni 2011 01:02:51 schreef Michael Scherer:
+&gt;<i> Le lundi 13 juin 2011 &#224; 15:51 +0300, Thomas Backlund a &#233;crit :
+</I>&gt;<i> &gt; Wolfgang Bornath skrev 13.6.2011 15:20:
+</I>&gt;<i> &gt; &gt; About the cycles:
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; The 9-months seem to be a compromise - but I start to ask why we need
+</I>&gt;<i> &gt; &gt; such a fixed statement (which it would be, once published). We need a
+</I>&gt;<i> &gt; &gt; schedule for each cycle, that's true. Without a schedule we would
+</I>&gt;<i> &gt; &gt; never finish anything. But how about taking 9 months only as a &quot;nice
+</I>&gt;<i> &gt; &gt; to meet&quot; target, leaving us the option to set a roadmap after setting
+</I>&gt;<i> &gt; &gt; the specs of the next release - we could then go for a 8 or 10 months
+</I>&gt;<i> &gt; &gt; roadmap, depending on the specs.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; This is somewhat like what I had in my mind to write too, but you beat
+</I>&gt;<i> &gt; me to it :)
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; It could allow us to adapt a little for upstream releases.
+</I>&gt;<i> &gt; But should we then decide that the limit is +/- 1 month ?
+</I>&gt;<i>
+</I>&gt;<i> There is 2 problem :
+</I>&gt;<i> - for release of what software ?
+</I>&gt;<i> - what if the upstream planning is wrong, and their releases is late
+</I>&gt;<i> ( as it happened when I was a trainee in Mandrakesoft, with xfree being
+</I>&gt;<i> 3 months late and the distribution still shipping a broken pre release )
+</I>&gt;<i>
+</I>&gt;<i> &gt; Obviously there will still be people complaining that &quot;you waited 10
+</I>&gt;<i> &gt; months... if you had extended with ~2 more weeks... &quot;this&quot; or &quot;that&quot;
+</I>&gt;<i> &gt; package would have been available too... and so on....
+</I>&gt;<i>
+</I>&gt;<i> Yes, there will be.
+</I>&gt;<i> So let's be realist, 9 months with +/- 1 month is just 10 months +
+</I>&gt;<i> people complaining to have 10,5 months.
+</I>&gt;<i>
+</I>&gt;<i> We will never use the -1 month, because there will always be something
+</I>&gt;<i> worth waiting.
+</I>
+actually, the real reason would be more to plan for whatever features you're
+going to implement and the time it takes to do them. if that's 8 months, it's
+8 months, if that's 9 or 10months, that's what it is.
+
+We proved that we can take a planning and follow it through, even the last
+release_critical one was solved _just_in_time_...
+
+imho, we need to decide now on a sort of 9month period, look at what we're
+going to do, then estimating how long it takes (with enough lenience), then
+make a real planning for that, and stick to it, if features are not ready,
+drop those features for next release, and make sure to fix all the
+release_criticals.
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="005567.html">[Mageia-dev] Release cycles proposals, and discussion
+</A></li>
+ <LI>Next message: <A HREF="005577.html">[Mageia-dev] Release cycles proposals, and discussion
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5576">[ date ]</a>
+ <a href="thread.html#5576">[ thread ]</a>
+ <a href="subject.html#5576">[ subject ]</a>
+ <a href="author.html#5576">[ 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>