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-July/006404.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2011-July/006404.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-July/006404.html | 154 |
1 files changed, 154 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-July/006404.html b/zarb-ml/mageia-dev/2011-July/006404.html new file mode 100644 index 000000000..ee2d35133 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006404.html @@ -0,0 +1,154 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Summary of the release cycle decision + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Summary%20of%20the%20release%20cycle%20decision&In-Reply-To=%3C20110706124407.GA15612%40sisay.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006401.html"> + <LINK REL="Next" HREF="006421.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Summary of the release cycle decision</H1> + <B>Michael scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Summary%20of%20the%20release%20cycle%20decision&In-Reply-To=%3C20110706124407.GA15612%40sisay.ephaone.org%3E" + TITLE="[Mageia-dev] Summary of the release cycle decision">misc at zarb.org + </A><BR> + <I>Wed Jul 6 14:44:07 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006401.html">[Mageia-dev] Repository question: where do we put non-free+tainted RPMs? +</A></li> + <LI>Next message: <A HREF="006421.html">[Mageia-dev] Summary of the release cycle decision +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6404">[ date ]</a> + <a href="thread.html#6404">[ thread ]</a> + <a href="subject.html#6404">[ subject ]</a> + <a href="author.html#6404">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hi + +So after reading all the feedback on the topic of release, here +are the conclusion of the discussion made by Anne and me : + + +- some people have expressed some concern about the fixed nature of the time based release. +While it was obvious, we do not plan to release with serious bug, especially if they cannot be +corrected after the release. And the whole question is to decide what is serious or not. I guess we can +do some more formal review of bugs in the release period. + +- despites trying to focus the discussion about the release cycle, the topic of the +support was touched. However, without more data, we couldn't evaluate much the requirement +in term of ressources. +Yet, several people proposed to follow the ubuntu model with LTS, or the suse one +with evergreen. As said before, this topic will be discussed soon ( likely once the backports one +are finished ), and we hope to be able to have more information since official support +was started. While the proposal is not even started, I guess it would be in the form of +having 1 distribution support for a longer time every X release, +and to try to take this in account for the features and softwares selected. + +- several persons on forum have also expressed the need for having a rock +solid release, which "simply" translate to have enough test and bugfixes. Yet, this +conflict with what some others persons wanted, ie newer softwares ( which by definition are +less tested, and so may be more subject to bugs ). How to solve +the dilemna is yet to be found, even if we have started with the current backport discussion. +The previous point about support could be also relevant to such issues, and we will take this in account. + +- and to finish, after reading everything the consensus seemed to be around having 9 months +for developpement was enough for a majority of people. + +Since we took one month for various things ( such as discussing everything ), we propose +the next release to be on 4th april, and start the cycle today. This is in the middle +of the week on purpose, to avoid the weekend. + +There is no exact planning yet ( so do not ask for now ), but it will be sent for next +week ( if everything goes well ). Once the planning is decided, a proper announce ( blog, forums, +etc ) should be done. + +-- +Michael Scherer +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006401.html">[Mageia-dev] Repository question: where do we put non-free+tainted RPMs? +</A></li> + <LI>Next message: <A HREF="006421.html">[Mageia-dev] Summary of the release cycle decision +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6404">[ date ]</a> + <a href="thread.html#6404">[ thread ]</a> + <a href="subject.html#6404">[ subject ]</a> + <a href="author.html#6404">[ 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> |