summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016434.html
blob: d7e452d38d99da3f5e155662e534b4e56f8c34ac (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
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20QA%20process%20for%20GNOME%203.4.2%20for%20Mageia%202&In-Reply-To=%3C4FD72A6F.1040400%40gmail.com%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="016433.html">
   <LINK REL="Next"  HREF="016551.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2</H1>
    <B>Claire Robinson</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20QA%20process%20for%20GNOME%203.4.2%20for%20Mageia%202&In-Reply-To=%3C4FD72A6F.1040400%40gmail.com%3E"
       TITLE="[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2">eeeemail at gmail.com
       </A><BR>
    <I>Tue Jun 12 13:39:27 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="016433.html">[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2
</A></li>
        <LI>Next message: <A HREF="016551.html">[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16434">[ date ]</a>
              <a href="thread.html#16434">[ thread ]</a>
              <a href="subject.html#16434">[ subject ]</a>
              <a href="author.html#16434">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On 12/06/12 12:19, andre999 wrote:
&gt;<i> Olav Vitters a &#233;crit :
</I>&gt;&gt;<i> For Mageia 2, I'd like to:
</I>&gt;&gt;<i> - get my act together and fix a bunch of bugs (a lot of wrong
</I>&gt;&gt;<i> suggests/requires, resulting in bugs&amp;crashers)
</I>&gt;&gt;<i> - provide GNOME 3.4.2 as update
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> But this concerns loads and loads of packages.
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> How to best proceed?
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> I saw mentioning that QA is really busy. How can I make this as simple
</I>&gt;&gt;<i> as possible for QA (not for myself)?
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> Should I:
</I>&gt;&gt;<i> #1 :
</I>&gt;&gt;<i> - first fix the various bugs
</I>&gt;&gt;<i> - provide each bug as update
</I>&gt;&gt;<i> then later:
</I>&gt;&gt;<i> - one massive GNOME 3.4.2 update?
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> #2 :
</I>&gt;&gt;<i> - do everything in one go (combine 3.4.2 update with the bugfixes)?
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> #3 :
</I>&gt;&gt;<i> - try and split out all the changes as much as possible (e.g.
</I>&gt;&gt;<i> evolution would need new evolution-data-server, so must be updated
</I>&gt;&gt;<i> at the same time).. but ideally go for filing a bug per
</I>&gt;&gt;<i> update/package?
</I>&gt;<i>
</I>&gt;<i> QA will probably have their answer, but it seems to me much easier for
</I>&gt;<i> QA to verify one or two packages at a time, meaning #3 as much as
</I>&gt;<i> possible, and then #1.
</I>&gt;<i> As far as how you do it for testing yourself (before presenting to QA),
</I>&gt;<i> you could use whatever approach seems easiest, but even there I would
</I>&gt;<i> think that #3 as much as possible would be easier. Anyway, that is how I
</I>&gt;<i> tend to approach things.
</I>&gt;<i> (#2 seems a potential nightmare, since you're bound to miss things.)
</I>&gt;<i>
</I>
Regarding the wrong requires/suggests these are probably best dealt with 
on separate bugs. They will receive proper attention that way and any 
affected by bug 2317 can hopefully be found so we don't have broken 
updates. That would be more difficult in one large update.

Other bugfixes and the big update I would say to follow KDE's example 
and list what has been fixed with bug numbers, packages being updated, 
srpm's. If the advisory is detailed it makes performing QA alot easier.

That is my first thought anyway. We're organising a QA meeting later 
this week, you're welcome to attend and ask the team. The time/date 
hasn't been finalised yet.

<A HREF="http://framadate.org/kg48uzoef3p9hitx">http://framadate.org/kg48uzoef3p9hitx</A>

Claire
</PRE>

























































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="016433.html">[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2
</A></li>
	<LI>Next message: <A HREF="016551.html">[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16434">[ date ]</a>
              <a href="thread.html#16434">[ thread ]</a>
              <a href="subject.html#16434">[ subject ]</a>
              <a href="author.html#16434">[ 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>