summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-September/007905.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-September/007905.html')
-rw-r--r--zarb-ml/mageia-dev/2011-September/007905.html147
1 files changed, 147 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-September/007905.html b/zarb-ml/mageia-dev/2011-September/007905.html
new file mode 100644
index 000000000..9aadd63d2
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-September/007905.html
@@ -0,0 +1,147 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Backports process (addendum to policy)
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20process%20%28addendum%20to%20policy%29&In-Reply-To=%3C4E69A770.5020809%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="007890.html">
+ <LINK REL="Next" HREF="007932.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Backports process (addendum to policy)</H1>
+ <B>andre999</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20process%20%28addendum%20to%20policy%29&In-Reply-To=%3C4E69A770.5020809%40laposte.net%3E"
+ TITLE="[Mageia-dev] Backports process (addendum to policy)">andre999.mga at laposte.net
+ </A><BR>
+ <I>Fri Sep 9 07:43:12 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="007890.html">[Mageia-dev] Backports process (addendum to policy)
+</A></li>
+ <LI>Next message: <A HREF="007932.html">[Mageia-dev] Backports process (addendum to policy)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#7905">[ date ]</a>
+ <a href="thread.html#7905">[ thread ]</a>
+ <a href="subject.html#7905">[ subject ]</a>
+ <a href="author.html#7905">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Samuel Verschelde a &#233;crit :
+&gt;<i> Le jeudi 8 septembre 2011 21:16:50, Florian Hubold a &#233;crit :
+</I>&gt;&gt;<i> Am 08.09.2011 13:08, schrieb Colin Guthrie:
+</I>&gt;&gt;&gt;<i> 'Twas brillig, and Samuel Verschelde at 08/09/11 11:59 did gyre and
+</I>&gt;<i> gimble:
+</I>&gt;&gt;&gt;&gt;<i> (QA Team and Triage team in CC, but please answer only to
+</I>&gt;&gt;&gt;&gt;<i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia-dev at mageia.org</A>)
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> I was asked to define a process for backports validation, so here is a
+</I>&gt;&gt;&gt;&gt;<i> proposal. We can discuss it a few days and then I'll add the result to
+</I>&gt;&gt;&gt;&gt;<i> the backports policy page.
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> Process for backports :
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> Triage:
+</I>&gt;&gt;&gt;&gt;<i> - identify backport requests
+</I>&gt;&gt;&gt;&gt;<i> - add &quot;Backport Request: &quot; in the bug report summary
+</I>&gt;&gt;&gt;&gt;<i> - add the &quot;backport&quot; keyword
+</I>&gt;&gt;&gt;&gt;<i> - assign to maintainer
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> The maintainer can refuse to do the backport :
+</I>&gt;&gt;&gt;&gt;<i> - doesn't want to maintain it =&gt; assign the bug report back to
+</I>&gt;&gt;&gt;&gt;<i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bugsquad at mageia.org</A> so that another packager can step in
+</I>&gt;&gt;&gt;&gt;<i> - has a good reason for not providing this backport (policy, possible
+</I>&gt;&gt;&gt;&gt;<i> breakage...) =&gt; close as wontfix
+</I>
+It would be a good idea to require giving the reason why refused, for clarity.
+ (e.g. &quot;Don't intend to maintain&quot; or &quot;Will conflict with version 123 of xyz&quot;,
+or whatever.)
+
+&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> Packager:
+</I>&gt;&gt;&gt;&gt;<i> - create bug report if not done already
+</I>&gt;&gt;&gt;&gt;<i> - submit to {core,nonfree,tainted}/backports_testing
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Is this straight from the cauldron tree in subversion?
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> - find a tester : original bug reporter when there is one, yourself if
+</I>&gt;&gt;&gt;&gt;<i> there's none, or ask in forums/irc/MLs...
+</I>&gt;&gt;&gt;&gt;<i> - once tested by at least one person (it must be said explicitly in the
+</I>&gt;&gt;&gt;&gt;<i> bug
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> report), hand it to QA :
+</I>&gt;&gt;&gt;&gt;<i> - make sure the bug report summary starts with &quot;Backport Request: &quot;
+</I>&gt;&gt;&gt;&gt;<i> or
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> &quot;Backport Candidate:&quot;
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> - add the &quot;backport&quot; keyword if missing
+</I>&gt;&gt;&gt;&gt;<i> - assign to <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">qa-bugs at ml.mageia.org</A>
+</I>&gt;&gt;&gt;&gt;<i> - list the source RPMs if there are several
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> - be ready to fix bugs and answer QA team questions
+</I>&gt;&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;&gt;<i> QA:
+</I>&gt;&gt;&gt;&gt;<i> - test backports the same way that we test updates. But don't forget
+</I>&gt;&gt;&gt;&gt;<i> that updates have a higher priority than that of backports.
+</I>&gt;&gt;&gt;&gt;<i> - move the packages from backports_testing to backports
+</I>&gt;&gt;&gt;<i>
+</I>&gt;&gt;&gt;<i> Just from a man power perspective this, could be a lot of work for QA
+</I>&gt;&gt;&gt;<i> (even at lower priority) but I cannot see a way to improve this without
+</I>&gt;&gt;&gt;<i> sacrificing quality control!
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> If the packager himself does basic testing and makes sure backport works,
+</I>&gt;&gt;<i> that would relieve QA from some work, no?
+</I>&gt;<i>
+</I>&gt;<i> In my opinion this is what a packager should always do, be it for an update, a
+</I>&gt;<i> backport, or a package in cauldron. But this doesn't remove the need for a QA
+</I>&gt;<i> validation if we want to guarantee a minimal level of quality.
+</I>
+Agree - that should always be done. QA is there to find what the packager
+might have missed.
+
+It seems an excellent backport policy - the weak link being the backport
+packager having to commit to support for the life of the release -- even though
+we can't garantie that it will be the case, that is a good requirement.
+
+&gt;<i>
+</I>&gt;<i> Samuel
+</I>&gt;<i>
+</I>
+--
+Andr&#233;
+</PRE>
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="007890.html">[Mageia-dev] Backports process (addendum to policy)
+</A></li>
+ <LI>Next message: <A HREF="007932.html">[Mageia-dev] Backports process (addendum to policy)
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#7905">[ date ]</a>
+ <a href="thread.html#7905">[ thread ]</a>
+ <a href="subject.html#7905">[ subject ]</a>
+ <a href="author.html#7905">[ 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>