blob: cd7140e416495fea4b0cd55c7d70762bcaca34d3 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
|
<!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=%3C4E68A237.6030900%40colin.guthr.ie%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="007859.html">
<LINK REL="Next" HREF="007862.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Backports process (addendum to policy)</H1>
<B>Colin Guthrie</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=%3C4E68A237.6030900%40colin.guthr.ie%3E"
TITLE="[Mageia-dev] Backports process (addendum to policy)">mageia at colin.guthr.ie
</A><BR>
<I>Thu Sep 8 13:08:39 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="007859.html">[Mageia-dev] Backports process (addendum to policy)
</A></li>
<LI>Next message: <A HREF="007862.html">[Mageia-dev] Backports process (addendum to policy)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7861">[ date ]</a>
<a href="thread.html#7861">[ thread ]</a>
<a href="subject.html#7861">[ subject ]</a>
<a href="author.html#7861">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>'Twas brillig, and Samuel Verschelde at 08/09/11 11:59 did gyre and gimble:
><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>
Is this straight from the cauldron tree in subversion?
><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>
Just from a man power perspective this, could be a lot of work for QA
(even at lower priority) but I cannot see a way to improve this without
sacrificing quality control!
Col
--
Colin Guthrie
mageia(at)colin.guthr.ie
<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
Day Job:
Tribalogic Limited [<A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>]
Open Source:
Mageia Contributor [<A HREF="http://www.mageia.org/">http://www.mageia.org/</A>]
PulseAudio Hacker [<A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>]
Trac Hacker [<A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>]
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="007859.html">[Mageia-dev] Backports process (addendum to policy)
</A></li>
<LI>Next message: <A HREF="007862.html">[Mageia-dev] Backports process (addendum to policy)
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#7861">[ date ]</a>
<a href="thread.html#7861">[ thread ]</a>
<a href="subject.html#7861">[ subject ]</a>
<a href="author.html#7861">[ 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>
|
