summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005845.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005845.html')
-rw-r--r--zarb-ml/mageia-dev/2011-June/005845.html104
1 files changed, 104 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005845.html b/zarb-ml/mageia-dev/2011-June/005845.html
new file mode 100644
index 000000000..ce3d60ccf
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-June/005845.html
@@ -0,0 +1,104 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process)
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Missing%20packages%20in%20Mageia%201.%20How%20to%20backport%3F%0A%20%28was%3A%20Finalizing%20update%20process%29&In-Reply-To=%3C1308490736.11316.245.camel%40akroma.ephaone.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="005826.html">
+ <LINK REL="Next" HREF="005833.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process)</H1>
+ <B>Michael Scherer</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Missing%20packages%20in%20Mageia%201.%20How%20to%20backport%3F%0A%20%28was%3A%20Finalizing%20update%20process%29&In-Reply-To=%3C1308490736.11316.245.camel%40akroma.ephaone.org%3E"
+ TITLE="[Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process)">misc at zarb.org
+ </A><BR>
+ <I>Sun Jun 19 15:38:56 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="005826.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process)
+</A></li>
+ <LI>Next message: <A HREF="005833.html">[Mageia-dev] Missing packages in Mageia 1. How to backport?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5845">[ date ]</a>
+ <a href="thread.html#5845">[ thread ]</a>
+ <a href="subject.html#5845">[ subject ]</a>
+ <a href="author.html#5845">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le samedi 18 juin 2011 &#224; 23:29 +0300, Ahmad Samir a &#233;crit :
+&gt;<i> So, is there a consensus about this yet? (note that the backports list
+</I>&gt;<i> of packages keeps growing in the mean time :)).
+</I>
+Well, my own impression was that the consensus is :
+the policy for version 1 is :
+- we can upload a missing package in update provided :
+ - it follow the same path as any update in term of QA, etc
+ - it was asked by someone, with a bug report or something like that,
+that it break update from 2010.1 ( so that part is specifically tested
+).
+ - there is no package in updates or release ( ie, the exception is
+only once )
+
+
+for version 2 and later :
+- new versions goes to backport, unless clearly expressed exceptions
+( bugfixes branchs, annoying upstreams ). The exact list of exception is
+roughly well agreed, minus details ( where the devil hide, obviously ).
+However, we didn't wrote it, nor decided on how to decide.
+
+So we would need :
+- a list of such exception written somewhere
+- a documented way to decide how to be in the exception list, ie a
+criteria list. I have attempted a proposal here :
+<A HREF="https://www.mageia.org/pipermail/mageia-dev/2011-June/005225.html">https://www.mageia.org/pipermail/mageia-dev/2011-June/005225.html</A> ,
+boklm attempted a slightly different one :
+<A HREF="https://www.mageia.org/pipermail/mageia-dev/2011-June/005373.html">https://www.mageia.org/pipermail/mageia-dev/2011-June/005373.html</A>
+
+Both are similar in spirit, so the question is just finding clear and
+useful criterias.
+
+
+Regarding backport policy, we didn't started to discuss much, but I
+wouldn't except to have it different from Mandriva for now, except what
+does &quot;supported&quot; mean, and the impact on the whole system ( as Christian
+noted, how to fill stuff in bugzilla, or the impact on Requires for a
+packaging policy to avoid mixing version ).
+
+That's something to keep for later, since that's already hard to follow
+current discussion ( especially with people who do not trim the email
+they answer to, and since ).
+
+But I will summarize the ideas and send a email after the one about
+release cycle.
+
+--
+Michael Scherer
+
+</PRE>
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="005826.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? (was: Finalizing update process)
+</A></li>
+ <LI>Next message: <A HREF="005833.html">[Mageia-dev] Missing packages in Mageia 1. How to backport?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5845">[ date ]</a>
+ <a href="thread.html#5845">[ thread ]</a>
+ <a href="subject.html#5845">[ subject ]</a>
+ <a href="author.html#5845">[ 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>