diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-September/007889.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-September/007889.html | 128 |
1 files changed, 128 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-September/007889.html b/zarb-ml/mageia-dev/2011-September/007889.html new file mode 100644 index 000000000..3e4c746a6 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/007889.html @@ -0,0 +1,128 @@ +<!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=%3C201109082212.26735.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="007887.html"> + <LINK REL="Next" HREF="007891.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports process (addendum to policy)</H1> + <B>Maarten Vanraes</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=%3C201109082212.26735.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Backports process (addendum to policy)">maarten.vanraes at gmail.com + </A><BR> + <I>Thu Sep 8 22:12:26 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="007887.html">[Mageia-dev] Backports process (addendum to policy) +</A></li> + <LI>Next message: <A HREF="007891.html">[Mageia-dev] Backports process (addendum to policy) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7889">[ date ]</a> + <a href="thread.html#7889">[ thread ]</a> + <a href="subject.html#7889">[ subject ]</a> + <a href="author.html#7889">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op donderdag 08 september 2011 12:59:10 schreef Samuel Verschelde: +><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> - 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 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> +</I>><i> Packager again: +</I>><i> - be ready to fix bugs : once you pushed a backport, you have to maintain +</I>><i> it until the distribution's end of life :) +</I>><i> +</I>><i> Does this seem a good process, from the packager, QA and triage point of +</I>><i> view? +</I>><i> +</I>><i> Best regards +</I>><i> +</I>><i> Samuel Verschelde +</I> + +anything about i586 vs x86_64 ? ie: at least 2 tests? or not? + +at least updates is this way, iinm... +</PRE> + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="007887.html">[Mageia-dev] Backports process (addendum to policy) +</A></li> + <LI>Next message: <A HREF="007891.html">[Mageia-dev] Backports process (addendum to policy) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7889">[ date ]</a> + <a href="thread.html#7889">[ thread ]</a> + <a href="subject.html#7889">[ subject ]</a> + <a href="author.html#7889">[ 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> |