diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/20101102/002836.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/20101102/002836.html | 138 |
1 files changed, 138 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/20101102/002836.html b/zarb-ml/mageia-discuss/20101102/002836.html new file mode 100644 index 000000000..de0b08eb4 --- /dev/null +++ b/zarb-ml/mageia-discuss/20101102/002836.html @@ -0,0 +1,138 @@ +<!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=%3C1288699997.12166.17.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="002830.html"> + <LINK REL="Next" HREF="002838.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-discuss] ISO 0 specification</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-discuss%40mageia.org?Subject=Re%3A%20%5BMageia-discuss%5D%20ISO%200%20specification&In-Reply-To=%3C1288699997.12166.17.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-discuss] ISO 0 specification">misc at zarb.org + </A><BR> + <I>Tue Nov 2 13:13:17 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="002830.html">[Mageia-discuss] ISO 0 specification +</A></li> + <LI>Next message: <A HREF="002838.html">[Mageia-discuss] ISO 0 specification +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2836">[ date ]</a> + <a href="thread.html#2836">[ thread ]</a> + <a href="subject.html#2836">[ subject ]</a> + <a href="author.html#2836">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le mardi 02 novembre 2010 à 09:20 +0100, Maarten Vanraes a écrit : +><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> +They are not more maintained on 2010.1 than on cooker. + +><i> personally, i'm against using cooker to make a stable ISO 0. +</I> +why that's what we do all the time, after a stabilisation period. It +worked fine for the last 7 years, and that's a part of the process that +is used by lots of distributions. ( have a devel tree, fork it for +release, bug fix, release it ). There is slightly different variations +( fedora and no frozen rawhide, debian and testing/stable/unstable ), +but all do the same, basically. + +><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> +But it would be less appealing, and this would make the life of the +communication team slightly difficult. It would also mean getting older +hardware support, older versions of various components ( like python, +for example ). + +And this would not save anything, as the bugfix work will have to be +done anyway sooner or later. + +More ever, the experience showed that if you give more time to fix bugs, +bugs just take more time to be fixed ( aka, we are lazy ). The more +visible evidence is the activity in Mandriva when a deadline appear "we +will now freeze the version update", where suddenly everybody update +everything ( while we could have done sooner ) + +And postponing to september ( ie 6 months later ) will be imho more +problematic, as this will add the current cooker breakage to the one +introduced by all the changes that people will want to push in the 6 +months ( gnome 3, etc, etc ). We have already experience with the +current 6 months cycles, but we do not really have with a 1 year cycle, +and this may cause trouble. + +So it is better to split the work into small time based chunks, because +that's something we know, and we should avoid surprise to start the +distribution. + +-- +Michael Scherer + +</PRE> + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="002830.html">[Mageia-discuss] ISO 0 specification +</A></li> + <LI>Next message: <A HREF="002838.html">[Mageia-discuss] ISO 0 specification +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#2836">[ date ]</a> + <a href="thread.html#2836">[ thread ]</a> + <a href="subject.html#2836">[ subject ]</a> + <a href="author.html#2836">[ 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> |