From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-September/007887.html | 129 ++++++++++++++++++++++++++ 1 file changed, 129 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-September/007887.html (limited to 'zarb-ml/mageia-dev/2011-September/007887.html') diff --git a/zarb-ml/mageia-dev/2011-September/007887.html b/zarb-ml/mageia-dev/2011-September/007887.html new file mode 100644 index 000000000..c3b193cde --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/007887.html @@ -0,0 +1,129 @@ + + + + [Mageia-dev] Backports process (addendum to policy) + + + + + + + + + +

[Mageia-dev] Backports process (addendum to policy)

+ Manuel Hiebel + manuel at hiebel.eu +
+ Thu Sep 8 21:30:35 CEST 2011 +

+
+ +
Le jeudi 08 septembre 2011 à 12:59 +0200, Samuel Verschelde a écrit :
+> (QA Team and Triage team in CC, but please answer only to 
+> mageia-dev at mageia.org)
+> 
+> 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
+
+For it's Ok.
+
+> The maintainer can refuse to do the backport :
+> - doesn't want to maintain it => assign the bug report back to 
+> bugsquad at mageia.org 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 qa-bugs at ml.mageia.org
+>   - 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
+
+-- 
+Manuel Hiebel (leuhmanu)
+
+
+ + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1