summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101016/001235.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101016/001235.html')
-rw-r--r--zarb-ml/mageia-dev/20101016/001235.html145
1 files changed, 145 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101016/001235.html b/zarb-ml/mageia-dev/20101016/001235.html
new file mode 100644
index 000000000..2926ddd99
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101016/001235.html
@@ -0,0 +1,145 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] How will be the realese cycle?
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C20101016110022.fef7dd67.gato2707%40yahoo.com.mx%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="001231.html">
+ <LINK REL="Next" HREF="001232.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] How will be the realese cycle?</H1>
+ <B>Fernando Parra</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3C20101016110022.fef7dd67.gato2707%40yahoo.com.mx%3E"
+ TITLE="[Mageia-dev] How will be the realese cycle?">gato2707 at yahoo.com.mx
+ </A><BR>
+ <I>Sat Oct 16 18:00:22 CEST 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001231.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI>Next message: <A HREF="001232.html">[Mageia-dev] Q: how long should we able to upgrade from?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1235">[ date ]</a>
+ <a href="thread.html#1235">[ thread ]</a>
+ <a href="subject.html#1235">[ subject ]</a>
+ <a href="author.html#1235">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On Sat, 16 Oct 2010 11:52:27 +0200
+Renaud MICHEL &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">r.h.michel+mageia-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org</A>&gt; wrote:
+
+&gt;<i> Hello
+</I>&gt;<i> On samedi 16 octobre 2010 at 05:00, Fernando Parra wrote :
+</I>&gt;<i> &gt; &gt; On Friday, 15 October 2010 03:48:56 Fernando Parra wrote:
+</I>&gt;<i> &gt; &gt; So, we must &quot;dumb down&quot; everything, and not provide openldap backports
+</I>&gt;<i> &gt; &gt; for people running servers who want a convenient way to run the
+</I>&gt;<i> &gt; &gt; software version that will allow them to file bugs upstream (OpenLDAP
+</I>&gt;<i> &gt; &gt; team doesn't respond to bugs filed on non-current releases)?
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Specially here the answer is obvious: The novice doesn't now what is
+</I>&gt;<i> &gt; OpenLDAP! and maybe he wont hear about it for the rest of his life. New
+</I>&gt;<i> &gt; versions of OpenLDAP should be stay available in the backports
+</I>&gt;<i> &gt; repository, not as an automatic available upgrade.
+</I>&gt;<i>
+</I>&gt;<i> Well, for example like OpenLDAP it is not a problem, because only users that
+</I>&gt;<i> need it will install it, and those that might need it are most likely aware
+</I>&gt;<i> what it implies to upgrade it to a newer version. So it will not bother
+</I>&gt;<i> other users if it is in backports or even updates, because as they won't
+</I>&gt;<i> have it installed, they won't be proposed to update.
+</I>&gt;<i>
+</I>&gt;<i> It is more of a concern for things like cups or dbus, which most users will
+</I>&gt;<i> use without knowing it, and won't know how to fix if it breaks (not even
+</I>&gt;<i> knowing which package actually broke).
+</I>&gt;<i>
+</I>&gt;<i> &gt; &gt; What do we do in the case where a new version of some software is
+</I>&gt;<i> &gt; &gt; available, and has been sent to cooker? How do we decide whether it
+</I>&gt;<i> &gt; &gt; should go to backports or not? And for which releases?
+</I>&gt;<i> &gt; &gt;
+</I>&gt;<i> &gt; &gt; (FYI, for Mandriva users can typically request backports in bugzilla or
+</I>&gt;<i> &gt; &gt; on IRC, but we may need better means).
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Ok, first at all, we must deicide what packages (not all of them!) will
+</I>&gt;<i> &gt; be at the Rolling Ligth model. After that, all this packages must have
+</I>&gt;<i> &gt; an appropriate path.
+</I>&gt;<i>
+</I>&gt;<i> I don't understand what you mean by &quot;appropriate path&quot;.
+</I>&gt;<i>
+</I>
+Well, if we are talking about a new model, I think we need to redefine what will be the way that's Mageia offer these particular (Rolling Light) packages. I'm not closed to any method in particular.
+
+&gt;<i> I think we should not decide before hand what packages will be backported,
+</I>&gt;<i> we should maybe have a (short) list of packages that must not be backported
+</I>&gt;<i> (like glibc) and then have backports either when contributors are willing to
+</I>&gt;<i> make (and test) them, or on request.
+</I>&gt;<i>
+</I>&gt;<i> Maybe we could also have a (short also) list of packages that we should
+</I>&gt;<i> really try (the packaging team could decide to dedicate some of his
+</I>&gt;<i> resources to that) to backport to the latest stable release, and maybe the
+</I>&gt;<i> previous latest.
+</I>&gt;<i> Such packages would be for example firefox or OOo, packages that we know are
+</I>&gt;<i> used by many (most) users, and many users are likely to want a newer
+</I>&gt;<i> version.
+</I>&gt;<i>
+</I>&gt;<i> &gt; Anyway, after decide what packages will be in the Rolling Light, The OS
+</I>&gt;<i> &gt; must be gentle with the user and show a Window with a Message like that:
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; There are available a new version of Firefox(as an example). Do you want
+</I>&gt;<i> &gt; to install it? NO, Maybe Later, Show me more information, Yes
+</I>&gt;<i>
+</I>&gt;<i> A little OT, but:
+</I>&gt;<i>
+</I>&gt;<i> Dialog windows should (almost) never have yes/no or ok/cancel choices,
+</I>&gt;<i> because when an user see a yes/ok choice, he generally interpret it as &quot;yes,
+</I>&gt;<i> I want to keep on doing what I was doing&quot;. (and I know I have done it some
+</I>&gt;<i> times myself)
+</I>&gt;<i>
+</I>&gt;<i> In your example, the No/yes should be labelled something like &quot;keep current
+</I>&gt;<i> version&quot; and &quot;install new version&quot;.
+</I>&gt;<i>
+</I>
+Ok, as more clear options, as it will be better.
+
+&gt;<i>
+</I>&gt;<i> cheers
+</I>&gt;<i> --
+</I>&gt;<i> Renaud Michel
+</I>&gt;<i>
+</I>
+Regards from Mexico
+--
+Fernando Parra &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">gato2707 at yahoo.com.mx</A>&gt;
+</PRE>
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001231.html">[Mageia-dev] How will be the realese cycle?
+</A></li>
+ <LI>Next message: <A HREF="001232.html">[Mageia-dev] Q: how long should we able to upgrade from?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1235">[ date ]</a>
+ <a href="thread.html#1235">[ thread ]</a>
+ <a href="subject.html#1235">[ subject ]</a>
+ <a href="author.html#1235">[ 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>