summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-July/006991.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-July/006991.html')
-rw-r--r--zarb-ml/mageia-dev/2011-July/006991.html110
1 files changed, 110 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-July/006991.html b/zarb-ml/mageia-dev/2011-July/006991.html
new file mode 100644
index 000000000..b09c89fc5
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-July/006991.html
@@ -0,0 +1,110 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] backports
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20backports&In-Reply-To=%3C201107252147.24786.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="006984.html">
+ <LINK REL="Next" HREF="006992.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] backports</H1>
+ <B>Maarten Vanraes</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20backports&In-Reply-To=%3C201107252147.24786.maarten.vanraes%40gmail.com%3E"
+ TITLE="[Mageia-dev] backports">maarten.vanraes at gmail.com
+ </A><BR>
+ <I>Mon Jul 25 21:47:24 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="006984.html">[Mageia-dev] John
+</A></li>
+ <LI>Next message: <A HREF="006992.html">[Mageia-dev] backports
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6991">[ date ]</a>
+ <a href="thread.html#6991">[ thread ]</a>
+ <a href="subject.html#6991">[ subject ]</a>
+ <a href="author.html#6991">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Hi,
+
+with regards to backports, users are complaining (they always do) that
+backports are taking too long.
+
+on the one hand almost everyone seems to agree that backports should be
+&quot;supported&quot; in some way or another... however, noone seems to want to
+actuallty put in the time to finalize that. (or at least that's how I see it)
+
+Since afair there is no real consensus, i suggest one of the following
+options, or possibly make this a vote, or have packaging team leaders (or
+board) decide this:
+
+A. backports are maintainers responsibility
+
+Every backport is tested or untested by maintainers discretion, (s)he decides
+how much testing it needs. We could still make a policy that there should be
+some tests.
+
+B. well established support like updates
+
+Similar QA like updates.
+
+
+then there is the matter of submission:
+
+A. We submit all backports from cauldron
+
+B. like updates, there's a separate section for backports
+
+C. backport submission is only allowed from the separate section, not from
+cauldron, if you want to backports from cauldron, you need to make the
+necessary steps yourself.
+
+
+personally, i favor B &amp; C; such as i think most of the people wanted; but if
+wanted, i can settle for A &amp; B.
+
+If someone from -sysadmin can find the time to make the SVN repos for backports
+(and testing), that would be awesome, so we can actually do some testing for
+it and get this show on the road.
+
+
+Maarten (aka AL13N)
+
+PS: i specifically left out updates to backports, as i personally feel that
+it's a backport, it just gets a newer release or version.
+</PRE>
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="006984.html">[Mageia-dev] John
+</A></li>
+ <LI>Next message: <A HREF="006992.html">[Mageia-dev] backports
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#6991">[ date ]</a>
+ <a href="thread.html#6991">[ thread ]</a>
+ <a href="subject.html#6991">[ subject ]</a>
+ <a href="author.html#6991">[ 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>