<!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 écrit :
><i> Le jeudi 8 septembre 2011 21:16:50, Florian Hubold a écrit :
</I>>><i> Am 08.09.2011 13:08, schrieb Colin Guthrie:
</I>>>><i> 'Twas brillig, and Samuel Verschelde at 08/09/11 11:59 did gyre and
</I>><i> gimble:
</I>>>>><i> (QA Team and Triage team in CC, but please answer only to
</I>>>>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia-dev at mageia.org</A>)
</I>>>>><i>
</I>>>>><i> I was asked to define a process for backports validation, so here is a
</I>>>>><i> proposal. We can discuss it a few days and then I'll add the result to
</I>>>>><i> the backports policy page.
</I>>>>><i>
</I>>>>><i> Process for backports :
</I>>>>><i>
</I>>>>><i> Triage:
</I>>>>><i> - identify backport requests
</I>>>>><i> - add "Backport Request: " in the bug report summary
</I>>>>><i> - add the "backport" keyword
</I>>>>><i> - assign to maintainer
</I>>>>><i>
</I>>>>><i> The maintainer can refuse to do the backport :
</I>>>>><i> - doesn't want to maintain it => assign the bug report back to
</I>>>>><i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bugsquad at mageia.org</A> so that another packager can step in
</I>>>>><i> - has a good reason for not providing this backport (policy, possible
</I>>>>><i> breakage...) => close as wontfix
</I>
It would be a good idea to require giving the reason why refused, for clarity.
(e.g. "Don't intend to maintain" or "Will conflict with version 123 of xyz",
or whatever.)
>>>><i>
</I>>>>><i> Packager:
</I>>>>><i> - create bug report if not done already
</I>>>>><i> - submit to {core,nonfree,tainted}/backports_testing
</I>>>><i>
</I>>>><i> Is this straight from the cauldron tree in subversion?
</I>>>><i>
</I>>>>><i> - find a tester : original bug reporter when there is one, yourself if
</I>>>>><i> there's none, or ask in forums/irc/MLs...
</I>>>>><i> - once tested by at least one person (it must be said explicitly in the
</I>>>>><i> bug
</I>>>>><i>
</I>>>>><i> report), hand it to QA :
</I>>>>><i> - make sure the bug report summary starts with "Backport Request: "
</I>>>>><i> or
</I>>>>><i>
</I>>>>><i> "Backport Candidate:"
</I>>>>><i>
</I>>>>><i> - add the "backport" keyword if missing
</I>>>>><i> - assign to <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">qa-bugs at ml.mageia.org</A>
</I>>>>><i> - list the source RPMs if there are several
</I>>>>><i>
</I>>>>><i> - be ready to fix bugs and answer QA team questions
</I>>>>><i>
</I>>>>><i> QA:
</I>>>>><i> - test backports the same way that we test updates. But don't forget
</I>>>>><i> that updates have a higher priority than that of backports.
</I>>>>><i> - move the packages from backports_testing to backports
</I>>>><i>
</I>>>><i> Just from a man power perspective this, could be a lot of work for QA
</I>>>><i> (even at lower priority) but I cannot see a way to improve this without
</I>>>><i> sacrificing quality control!
</I>>><i>
</I>>><i> If the packager himself does basic testing and makes sure backport works,
</I>>><i> that would relieve QA from some work, no?
</I>><i>
</I>><i> In my opinion this is what a packager should always do, be it for an update, a
</I>><i> backport, or a package in cauldron. But this doesn't remove the need for a QA
</I>><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.
><i>
</I>><i> Samuel
</I>><i>
</I>
--
André
</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>