summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/006041.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006041.html')
-rw-r--r--zarb-ml/mageia-dev/2011-June/006041.html139
1 files changed, 139 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006041.html b/zarb-ml/mageia-dev/2011-June/006041.html
new file mode 100644
index 000000000..150a43cbe
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-June/006041.html
@@ -0,0 +1,139 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Update of backport, policy proposal
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Update%20of%20backport%2C%20policy%20proposal&In-Reply-To=%3CBANLkTim_8WVwniXZ-eq_jrKtLdoZ8Ru%3D2w%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="006036.html">
+ <LINK REL="Next" HREF="006042.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Update of backport, policy proposal</H1>
+ <B>Wolfgang Bornath</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Update%20of%20backport%2C%20policy%20proposal&In-Reply-To=%3CBANLkTim_8WVwniXZ-eq_jrKtLdoZ8Ru%3D2w%40mail.gmail.com%3E"
+ TITLE="[Mageia-dev] Update of backport, policy proposal">molch.b at googlemail.com
+ </A><BR>
+ <I>Sun Jun 26 14:49:37 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="006036.html">[Mageia-dev] Update of backport, policy proposal
+</A></li>
+ <LI>Next message: <A HREF="006042.html">[Mageia-dev] Update of backport, policy proposal
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6041">[ date ]</a>
+ <a href="thread.html#6041">[ thread ]</a>
+ <a href="subject.html#6041">[ subject ]</a>
+ <a href="author.html#6041">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>2011/6/26 Michael Scherer &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>&gt;:
+&gt;<i> Le dimanche 26 juin 2011 &#224; 11:58 +0300, atilla ontas a &#233;crit :
+</I>&gt;&gt;<i> 2011/6/26 Wolfgang Bornath &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">molch.b at googlemail.com</A>&gt;:
+</I>&gt;&gt;<i> &gt; A short reality check from userside:
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; If foo-1.0 is in Mageia 1 and foo-1.1 is released upstream
+</I>&gt;&gt;<i> &gt; &#160;- foo-1.1 will likely be integrated in Cauldron very soon after
+</I>&gt;&gt;<i> &gt; &#160;- users will request to have foo-1.1 in Mageia 1
+</I>&gt;&gt;<i> &gt; &#160;- if Mageia will not provide it then there will soon be local
+</I>&gt;&gt;<i> &gt; repositories where local packagers will do a &quot;backport&quot; for their
+</I>&gt;&gt;<i> &gt; friends.
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; This may not be what Mageia backport policy will allow but we can not
+</I>&gt;&gt;<i> &gt; avoid people doing and using this, no matter how many warning signs we
+</I>&gt;&gt;<i> &gt; will publish. This has to be taken into account here.
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; When a policy is found it has to be communicated very well, especially
+</I>&gt;&gt;<i> &gt; if that policy means that the user can not have foo-1.1 in his stable
+</I>&gt;&gt;<i> &gt; Mageia 1.
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; This is important because former Mandriva users were used to get
+</I>&gt;&gt;<i> &gt; almost all new versions backported, if not officially then in 3rd
+</I>&gt;&gt;<i> &gt; party repos like MIB or MUD.
+</I>&gt;&gt;<i> &gt;
+</I>&gt;&gt;<i> &gt; --
+</I>&gt;&gt;<i> &gt; wobo
+</I>&gt;&gt;<i> &gt;
+</I>&gt;<i>
+</I>&gt;&gt;<i> As wobo mentioned, people like latest and greatest software. I think,
+</I>&gt;&gt;<i> except a few users will use unofficial 3rd party repos to get latest
+</I>&gt;&gt;<i> software. While i was maintaining MVT (Mandriva Turkiye) repository,
+</I>&gt;&gt;<i> our users asked for GNOME 2.32 while Mandriva have GNOME 2.30 on
+</I>&gt;&gt;<i> official release.
+</I>&gt;<i>
+</I>&gt;<i> And others people mentioned that people want also stable software and do
+</I>&gt;<i> not want changes. But as I said, what people want is not as important
+</I>&gt;<i> than what we can do, and so the decision is in the end of those that do
+</I>&gt;<i> the work rather than what people want, because if no one does the work,
+</I>&gt;<i> nothing happen.
+</I>
+Well, in principle this is correct, not in this case as I have
+explained as a very common example. You can decide whatever you want,
+if a user wants a certain package and his friend will pack it for him
+and puts it up on a server, publishing the existence - then you will
+see what happens. You know by experience how popular such 3rd-party
+repos can become (see MIB, MUD), just because somebody had a different
+view than the official view.
+In short: no matter what is more important or not, you have to find a
+compromise between the (understandable) search for optimal workflow,
+security on one side and the real world of the users on the other. I
+think, the key here is non-technical communication of the
+circumstances, like &quot;why we can't have foo 1.2 as backport from
+Cauldron to Mageia 1&quot;.
+
+--
+wobo
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="006036.html">[Mageia-dev] Update of backport, policy proposal
+</A></li>
+ <LI>Next message: <A HREF="006042.html">[Mageia-dev] Update of backport, policy proposal
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6041">[ date ]</a>
+ <a href="thread.html#6041">[ thread ]</a>
+ <a href="subject.html#6041">[ subject ]</a>
+ <a href="author.html#6041">[ 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>