diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005539.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005539.html | 272 |
1 files changed, 272 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005539.html b/zarb-ml/mageia-dev/2011-June/005539.html new file mode 100644 index 000000000..3582c40c5 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005539.html @@ -0,0 +1,272 @@ +<!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=%3C201106131932.40202.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005542.html"> + <LINK REL="Next" HREF="005546.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Release cycles proposals, and discussion</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycles%20proposals%2C%20and%20discussion&In-Reply-To=%3C201106131932.40202.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Release cycles proposals, and discussion">maarten.vanraes at gmail.com + </A><BR> + <I>Mon Jun 13 19:32:40 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005542.html">[Mageia-dev] Release cycles proposals, and discussion +</A></li> + <LI>Next message: <A HREF="005546.html">[Mageia-dev] GNOME3 ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5539">[ date ]</a> + <a href="thread.html#5539">[ thread ]</a> + <a href="subject.html#5539">[ subject ]</a> + <a href="author.html#5539">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op maandag 13 juni 2011 18:51:40 schreef Ron: +><i> I will say my part and I'm gone... +</I>><i> I don't understand why everyone is acting like a rolling release is going +</I>><i> to put so much strain on the project. What is so hard about developing in +</I>><i> one place and allowing the updates to trickle down is so hard? It almost +</I>><i> seems to me that you want to ask the opinion of people, but don't want to +</I>><i> hear. And what is this posting here? I don't even know how to use this +</I>><i> thing and yet I had to signup to get my voice heard because this is the +</I>><i> way you want to do things? I don't understand where the whole community +</I>><i> fits into this here right now, I think I actually say a lot when I say +</I>><i> that many people want a rolling release.... It just seems the developers +</I>><i> will have the way here... Why ask in the first place? Really? I am leaving +</I>><i> the list and sorry about the HTML in my emails, must be a yahoo thing +</I>><i> because I did not use HTML... Again I don't know how to use this thing and +</I>><i> should not have been forced to. I would also say that I, for 1 will not be +</I>><i> staying if you are going to do a release cycle only... I have loads of +</I>><i> options if I just want snapshots of what's going on in the Linux world.... +</I>><i> Arch gives me so much more and I had hopes of switching to this with a +</I>><i> release model that made sense... But it seems we won't and we will just +</I>><i> become yet another XXX release cycle distribution with no clear anything +</I>><i> that sets us apart from X. On you, I'm gone and thanks for hearing me and +</I>><i> sorry if my postings were done wrong.... +</I> +complete rolling release would put a QA strain on each of the levels. think +about it, it's not only the current package being updated, but also the +combinations with other packages. (AND also all the long time supported +versions) + +This would mean that for each package being release, it'll have to work with +the current set of other packages, but also with the packages you'll be doing +next. + +if you have this constant level of QA, you need alot of resources (which we +don't have in QA), and as an extra result, you'll not have the same level of +QA you could have, when you're doing a release. + +it's much easier (as devs) to just choose a subset of packages, and test those +out. + +if you have X QA-devs, and you have 1 subset of versions of packages, you can +test alot more than if you have several versions of several packages that need +to work all with each other in almost any combinations... + +not to mention that you need an extra step with QA to put a "group" of +packages from one level to the next... + +sorry, but with our current resources, i vote no. i want current resources to +be used much more efficiently than with a rolling release. +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005542.html">[Mageia-dev] Release cycles proposals, and discussion +</A></li> + <LI>Next message: <A HREF="005546.html">[Mageia-dev] GNOME3 ? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5539">[ date ]</a> + <a href="thread.html#5539">[ thread ]</a> + <a href="subject.html#5539">[ subject ]</a> + <a href="author.html#5539">[ 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> |