diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005568.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005568.html | 188 |
1 files changed, 188 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005568.html b/zarb-ml/mageia-dev/2011-June/005568.html new file mode 100644 index 000000000..9d2faf178 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005568.html @@ -0,0 +1,188 @@ +<!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=%3C1308007906.24304.89.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005570.html"> + <LINK REL="Next" HREF="005571.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Release cycles proposals, and discussion</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycles%20proposals%2C%20and%20discussion&In-Reply-To=%3C1308007906.24304.89.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] Release cycles proposals, and discussion">misc at zarb.org + </A><BR> + <I>Tue Jun 14 01:31:46 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005570.html">[Mageia-dev] Release cycles proposals, and discussion +</A></li> + <LI>Next message: <A HREF="005571.html">[Mageia-dev] Release cycles proposals, and discussion +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5568">[ date ]</a> + <a href="thread.html#5568">[ thread ]</a> + <a href="subject.html#5568">[ subject ]</a> + <a href="author.html#5568">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le lundi 13 juin 2011 à 14:20 +0200, Wolfgang Bornath a écrit : + +><i> The 9-months seem to be a compromise - but I start to ask why we need +</I>><i> such a fixed statement (which it would be, once published). We need a +</I>><i> schedule for each cycle, that's true. Without a schedule we would +</I>><i> never finish anything. But how about taking 9 months only as a "nice +</I>><i> to meet" target, leaving us the option to set a roadmap after setting +</I>><i> the specs of the next release - we could then go for a 8 or 10 months +</I>><i> roadmap, depending on the specs. +</I> +As I said to Thomas, we will never use the 8 months option. If we say +"we have selected less features to finish sooner", people will just ask +for more features, and will say "why do you want to finish sooner, I +prefer to have feature and wait 1 month more". + +In fact, the same would go for 9 to 10 if we start to propose the +possibility. + +And deciding that we will decide later is not really deciding. We should +select features based on time needed to implement them and how much time +we can devote, not the contrary especially since no one will ever be +able to give precise timing for anything, so one month of difference +would be difficult to justify. + +And I think we can already decide to release 1 week later if a +release_critical bug appears. Fedora 15 for example was 2 weeks late, +because they changed the release date twice after having seen some +problem (<A HREF="http://fedoraproject.org/wiki/Releases/15/Schedule">http://fedoraproject.org/wiki/Releases/15/Schedule</A> ). + +And we did it more than once at Mandriva. + +><i> This being said, I am a friend of a rolling release like ArchLinux, +</I>><i> but I fear that our main target group is not up to this. Despite of +</I>><i> having to "burn yet another DVD" as somebody pointed out, the majority +</I>><i> seems to see this as normal and a good way. Of course I may be totally +</I>><i> wrong with this assessment! +</I> +Maybe people should maybe start to trust more mgaonline to do upgrade, +there is nothing that pacman does that urpmi don't regarding upgrade, +there is no magic involved : +- people should test before the release and fill bug reports. + +That's the secret behind debian upgrade, people just do lots of tests +for that either automated ( using something like piupart +( <A HREF="http://wiki.debian.org/piuparts">http://wiki.debian.org/piuparts</A> ) ), or manual and lots of people do +full system upgrade long before the release ( and not only after ). + +-- +Michael Scherer + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005570.html">[Mageia-dev] Release cycles proposals, and discussion +</A></li> + <LI>Next message: <A HREF="005571.html">[Mageia-dev] Release cycles proposals, and discussion +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5568">[ date ]</a> + <a href="thread.html#5568">[ thread ]</a> + <a href="subject.html#5568">[ subject ]</a> + <a href="author.html#5568">[ 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> |