diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20101103/002864.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20101103/002864.html | 153 |
1 files changed, 153 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20101103/002864.html b/zarb-ml/mageia-discuss/20101103/002864.html new file mode 100644 index 000000000..2539e2b7e --- /dev/null +++ b/zarb-ml/mageia-discuss/20101103/002864.html @@ -0,0 +1,153 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-discuss] ISO 0 specification + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20ISO%200%20specification&In-Reply-To=%3C4CD1752E.10200%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="002868.html"> + <LINK REL="Next" HREF="002870.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] ISO 0 specification</H1> + <B>andre999</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20ISO%200%20specification&In-Reply-To=%3C4CD1752E.10200%40laposte.net%3E" + TITLE="[Mageia-discuss] ISO 0 specification">andr55 at laposte.net + </A><BR> + <I>Wed Nov 3 15:43:58 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="002868.html">[Mageia-discuss] Suggestions for the ISO +</A></li> + <LI>Next message: <A HREF="002870.html">[Mageia-discuss] Suggestions for the ISO +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2864">[ date ]</a> + <a href="thread.html#2864">[ thread ]</a> + <a href="subject.html#2864">[ subject ]</a> + <a href="author.html#2864">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Michael Scherer a écrit : +><i> Le mardi 02 novembre 2010 à 09:20 +0100, Maarten Vanraes a écrit : +</I>><i> +</I>>><i> I read the full meeting logs from 25/10, and i noticed tmb saying: +</I>>><i> +</I>>><i> "pretty much a cooker snapshot" +</I>>><i> +</I>>><i> +</I>>><i> I donno how far you're going to take this; but i thought we would be getting a +</I>>><i> new version out ASAP. +</I>>><i> +</I>>><i> in my understanding, we would get a 2010.1 snapshot and use it to build the +</I>>><i> first ISO. +</I>>><i> +</I>>><i> and use the cooker snapshot to get a cauldron. +</I>>><i> +</I>>><i> imo the cooker is sooo unstable and broken, we will not be able to get a +</I>>><i> working ISO from it, that is more or less stable in this timeframe. +</I>>><i> +</I>>><i> eg: +</I>>><i> * KDE +</I>>><i> * glib +</I>>><i> * perl +</I>>><i> * python +</I>>><i> * RPM +</I>>><i> * ... +</I>>><i> +</I>>><i> +</I>>><i> most of these will get fixed, in time; but what about ALL the packages +</I>>><i> depending on that? most of the packages aren't even maintained... +</I>>><i> +</I>><i> They are not more maintained on 2010.1 than on cooker. +</I>><i> +</I>>><i> personally, i'm against using cooker to make a stable ISO 0. +</I>>><i> +</I>><i> why that's what we do all the time, after a stabilisation period. It +</I>><i> worked fine for the last 7 years, and that's a part of the process that +</I>><i> is used by lots of distributions. ( have a devel tree, fork it for +</I>><i> release, bug fix, release it ). There is slightly different variations +</I>><i> ( fedora and no frozen rawhide, debian and testing/stable/unstable ), +</I>><i> but all do the same, basically. +</I>><i> +</I>>><i> rebranding a 2010.1 will be lots more stable; and maintime we will have the +</I>>><i> time to make cauldron (from cooker) into something good, so we will be able to +</I>>><i> make a release based on cauldron on the 18th of september. +</I>>><i> +</I>><i> But it would be less appealing, and this would make the life of the +</I>><i> communication team slightly difficult. It would also mean getting older +</I>><i> hardware support, older versions of various components ( like python, +</I>><i> for example ). +</I>><i> +</I>><i> And this would not save anything, as the bugfix work will have to be +</I>><i> done anyway sooner or later. +</I>><i> +</I>><i> More ever, the experience showed that if you give more time to fix bugs, +</I>><i> bugs just take more time to be fixed ( aka, we are lazy ). The more +</I>><i> visible evidence is the activity in Mandriva when a deadline appear "we +</I>><i> will now freeze the version update", where suddenly everybody update +</I>><i> everything ( while we could have done sooner ) +</I>><i> +</I>><i> And postponing to september ( ie 6 months later ) will be imho more +</I>><i> problematic, as this will add the current cooker breakage to the one +</I>><i> introduced by all the changes that people will want to push in the 6 +</I>><i> months ( gnome 3, etc, etc ). We have already experience with the +</I>><i> current 6 months cycles, but we do not really have with a 1 year cycle, +</I>><i> and this may cause trouble. +</I>><i> +</I>><i> So it is better to split the work into small time based chunks, because +</I>><i> that's something we know, and we should avoid surprise to start the +</I>><i> distribution. +</I>><i> +</I> +I agree to go with cooker. +1) We have a lot of experienced Mandriva people with Mageia who propose +cooker. + +2) We have the enthusiasme of many new contributors for a community +based distro. +Many, like myself, have valuable experience elsewhere. + +3) We will be starting with a more up-to-date base. +Thus we can avoid much complication with backports, etc. + +4) The process is the same as for Mandriva, and very similar to other +major distros. +When starting a new distro, it is better to minimize major changes in +the process, if there isn't a compelling reason to do so. + +I fail to see the down side. + +- André +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002868.html">[Mageia-discuss] Suggestions for the ISO +</A></li> + <LI>Next message: <A HREF="002870.html">[Mageia-discuss] Suggestions for the ISO +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2864">[ date ]</a> + <a href="thread.html#2864">[ thread ]</a> + <a href="subject.html#2864">[ subject ]</a> + <a href="author.html#2864">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-discuss">More information about the Mageia-discuss +mailing list</a><br> +</body></html> |