diff options
author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
---|---|---|
committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2011-September/007886.html | |
parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip |
Diffstat (limited to 'zarb-ml/mageia-dev/2011-September/007886.html')
-rw-r--r-- | zarb-ml/mageia-dev/2011-September/007886.html | 119 |
1 files changed, 119 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-September/007886.html b/zarb-ml/mageia-dev/2011-September/007886.html new file mode 100644 index 000000000..79155b0c5 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/007886.html @@ -0,0 +1,119 @@ +<!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=%3C4E6914A2.3080303%40arcor.de%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="007864.html"> + <LINK REL="Next" HREF="007890.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports process (addendum to policy)</H1> + <B>Florian Hubold</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=%3C4E6914A2.3080303%40arcor.de%3E" + TITLE="[Mageia-dev] Backports process (addendum to policy)">doktor5000 at arcor.de + </A><BR> + <I>Thu Sep 8 21:16:50 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="007864.html">[Mageia-dev] Backports process (addendum to policy) +</A></li> + <LI>Next message: <A HREF="007890.html">[Mageia-dev] Backports process (addendum to policy) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7886">[ date ]</a> + <a href="thread.html#7886">[ thread ]</a> + <a href="subject.html#7886">[ subject ]</a> + <a href="author.html#7886">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Am 08.09.2011 13:08, schrieb Colin Guthrie: +><i> 'Twas brillig, and Samuel Verschelde at 08/09/11 11:59 did gyre and 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 the +</I>>><i> 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>>><i> +</I>>><i> Packager: +</I>>><i> - create bug report if not done already +</I>>><i> - submit to {core,nonfree,tainted}/backports_testing +</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 there's +</I>>><i> none, or ask in forums/irc/MLs... +</I>>><i> - once tested by at least one person (it must be said explicitly in the bug +</I>>><i> report), hand it to QA : +</I>>><i> - make sure the bug report summary starts with "Backport Request: " or +</I>>><i> "Backport Candidate:" +</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> - 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 that +</I>>><i> updates have a higher priority than that of backports. +</I>>><i> - move the packages from backports_testing to backports +</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>If the packager himself does basic testing and makes sure backport works, +that would relieve QA from some work, no? +</PRE> + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="007864.html">[Mageia-dev] Backports process (addendum to policy) +</A></li> + <LI>Next message: <A HREF="007890.html">[Mageia-dev] Backports process (addendum to policy) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7886">[ date ]</a> + <a href="thread.html#7886">[ thread ]</a> + <a href="subject.html#7886">[ subject ]</a> + <a href="author.html#7886">[ 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> |