diff options
author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
---|---|---|
committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2011-June/005844.html | |
parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
download | archives-1be510f9529cb082f802408b472a77d074b394c0.tar archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2 archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz archives-1be510f9529cb082f802408b472a77d074b394c0.zip |
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005844.html')
-rw-r--r-- | zarb-ml/mageia-dev/2011-June/005844.html | 149 |
1 files changed, 149 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005844.html b/zarb-ml/mageia-dev/2011-June/005844.html new file mode 100644 index 000000000..9472ea871 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005844.html @@ -0,0 +1,149 @@ +<!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=%3CBANLkTimy0TMnFZxk_x-7XYo070Cgf6VOeA%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005841.html"> + <LINK REL="Next" HREF="005847.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Release cycles proposals, and discussion</H1> + <B>mammig_linux mammig_linux</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycles%20proposals%2C%20and%20discussion&In-Reply-To=%3CBANLkTimy0TMnFZxk_x-7XYo070Cgf6VOeA%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Release cycles proposals, and discussion">mammig.linux at gmail.com + </A><BR> + <I>Sun Jun 19 15:23:36 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005841.html">[Mageia-dev] Release cycles proposals, and discussion +</A></li> + <LI>Next message: <A HREF="005847.html">[Mageia-dev] Release cycles proposals, and discussion +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5844">[ date ]</a> + <a href="thread.html#5844">[ thread ]</a> + <a href="subject.html#5844">[ subject ]</a> + <a href="author.html#5844">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hello, + +The discussion about the "Mageia life cycle" start few days ago on the +forum of the French user community of Mageia ( +<A HREF="http://www.mageialinux-online.org/forum/topic-10576+cycle-de-vie-de-mageia.php">http://www.mageialinux-online.org/forum/topic-10576+cycle-de-vie-de-mageia.php</A> +:<i> for those who read French ) +</I> +tTo put all the answers in a nutshell, i will say that users rather +having a new version if that bring big changes. +If the goal is to have a "windows like new version" ( with a new +design, new bugs, new system sounds, "please buy a new printer/scanner +because the new driver will never exist" or "please buy a new computer +because yours is too old/not enough memory"... and no fundamental +changes on the OS ) or something like : +Mageia(n) = Mageia(n-1) - some bugs + new design + some updates +then it's useless to have a new version each x month. + +Users wants a good, strong, and long life OS. +Those who like to change the design will be happy if they have +something like "task-newdesign.RPM" +those who like news or updates will be happy with update and backports +repository. + +Currently, we just put the suitcase on the floor. ( sorry, bad +translation of a french idiom ;)) +The website is "temporary", like the wiki and like a lot of things. +It's hard to find new volunteers... So... We needn't to have the eyes +bigger than the stomach ( sorry, bad translation of a French idiom +O:)) +Let's take time for opening the suitcase... having a good multilingual +web site with an easy management, a "not temporary" wiki, correcting +bugs, maybe make more test, create the missing and ask packages, +create stronger teams with more people. Maybe we can think of a new +way of working ( like the idea of "Proofreading" in i18n teams )... + +Currently I help anaselli in his project of "educative Mageia +version", maybe it should be great to have others version of Mageia ( +like a "server" version for example ). + +Greeting, +mammig + +PS : I think it's a good thing to have the opinion of users about +that, even if they are not english. I will not make a translation of +each message, I guess a small summary is enough. + +2011/6/19 Oliver Burger <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">oliver.bgr at googlemail.com</A>>: +><i> andre999 <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">andr55 at laposte.net</A>> schrieb am 19.06.2011 +</I>><i> +</I>>><i> Another thought about the amended freeze process. +</I>><i> +</I>>><i> Have you noticed how packagers sometimes set off an exchange of 10 +</I>><i> +</I>>><i> or more emails in attempts to get a package into the release +</I>><i> +</I>>><i> during the freeze ? +</I>><i> +</I>>><i> The packager wants to submit, but they can't because cauldron is +</I>><i> +</I>>><i> frozen. Maybe if only pre-release were frozen, but cauldron open, +</I>><i> +</I>>><i> they would accept submitting to cauldron after only 1 or 2 +</I>><i> +</I>>><i> exchanges. They would have the at least partial satisfaction of +</I>><i> +</I>>><i> being able to submit their package (instead of waiting, and doing +</I>><i> +</I>>><i> something else, probably elsewhere), and others would have been +</I>><i> +</I>>><i> releaved of the hassle of dealing with their repeated requests. I +</I>><i> +</I>>><i> think that would be more motivating for the packager in question, +</I>><i> +</I>>><i> as well as the others involved. And packagers would avoid wasting +</I>><i> +</I>>><i> both time and energy. +</I>><i> +</I>><i> I don't know. I think most freeze push requests were due to the fact, that +</I>><i> packagers wanted to have their baby in the release. +</I>><i> +</I>><i> Because every packager knows, he only has to wait some days to submit it to +</I>><i> Cauldron again. +</I>><i> +</I>><i> So I don't think any packager would be any the happier by this solution. +</I>><i> +</I>><i> I have to agree with misc. It would only mean having more work. +</I>><i> +</I>><i> Oliver +</I></PRE> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005841.html">[Mageia-dev] Release cycles proposals, and discussion +</A></li> + <LI>Next message: <A HREF="005847.html">[Mageia-dev] Release cycles proposals, and discussion +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5844">[ date ]</a> + <a href="thread.html#5844">[ thread ]</a> + <a href="subject.html#5844">[ subject ]</a> + <a href="author.html#5844">[ 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> |