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/007859.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/007859.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-September/007859.html | 132 |
1 files changed, 132 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-September/007859.html b/zarb-ml/mageia-dev/2011-September/007859.html new file mode 100644 index 000000000..bf1d3b579 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/007859.html @@ -0,0 +1,132 @@ +<!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=%3C201109081259.10996.stormi%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="007903.html"> + <LINK REL="Next" HREF="007861.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports process (addendum to policy)</H1> + <B>Samuel Verschelde</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=%3C201109081259.10996.stormi%40laposte.net%3E" + TITLE="[Mageia-dev] Backports process (addendum to policy)">stormi at laposte.net + </A><BR> + <I>Thu Sep 8 12:59:10 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="007903.html">[Mageia-dev] Copying dependencies from Release to Updates Testing +</A></li> + <LI>Next message: <A HREF="007861.html">[Mageia-dev] Backports process (addendum to policy) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7859">[ date ]</a> + <a href="thread.html#7859">[ thread ]</a> + <a href="subject.html#7859">[ subject ]</a> + <a href="author.html#7859">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>(QA Team and Triage team in CC, but please answer only to +<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia-dev at mageia.org</A>) + +I was asked to define a process for backports validation, so here is a +proposal. We can discuss it a few days and then I'll add the result to the +backports policy page. + +Process for backports : + +Triage: +- identify backport requests +- add "Backport Request: " in the bug report summary +- add the "backport" keyword +- assign to maintainer + +The maintainer can refuse to do the backport : +- doesn't want to maintain it => assign the bug report back to +<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bugsquad at mageia.org</A> so that another packager can step in +- has a good reason for not providing this backport (policy, possible +breakage...) => close as wontfix + +Packager: +- create bug report if not done already +- submit to {core,nonfree,tainted}/backports_testing +- find a tester : original bug reporter when there is one, yourself if there's +none, or ask in forums/irc/MLs... +- once tested by at least one person (it must be said explicitly in the bug +report), hand it to QA : + - make sure the bug report summary starts with "Backport Request: " or +"Backport Candidate: " + - add the "backport" keyword if missing + - assign to <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">qa-bugs at ml.mageia.org</A> + - list the source RPMs if there are several +- be ready to fix bugs and answer QA team questions + +QA: +- test backports the same way that we test updates. But don't forget that +updates have a higher priority than that of backports. +- move the packages from backports_testing to backports + +Packager again: +- be ready to fix bugs : once you pushed a backport, you have to maintain it +until the distribution's end of life :) + +Does this seem a good process, from the packager, QA and triage point of view? + +Best regards + +Samuel Verschelde +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="007903.html">[Mageia-dev] Copying dependencies from Release to Updates Testing +</A></li> + <LI>Next message: <A HREF="007861.html">[Mageia-dev] Backports process (addendum to policy) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#7859">[ date ]</a> + <a href="thread.html#7859">[ thread ]</a> + <a href="subject.html#7859">[ subject ]</a> + <a href="author.html#7859">[ 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> |