summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016742.html
blob: 9eacfb2fcacaa5ce2155d11ba62b05ab426962ea (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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%0A%20like%20--search-media&In-Reply-To=%3C4FE44AE4.9090402%40mageia.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="016746.html">
   <LINK REL="Next"  HREF="016744.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media</H1>
    <B>Thomas Backlund</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%0A%20like%20--search-media&In-Reply-To=%3C4FE44AE4.9090402%40mageia.org%3E"
       TITLE="[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media">tmb at mageia.org
       </A><BR>
    <I>Fri Jun 22 12:37:24 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="016746.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
        <LI>Next message: <A HREF="016744.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16742">[ date ]</a>
              <a href="thread.html#16742">[ thread ]</a>
              <a href="subject.html#16742">[ subject ]</a>
              <a href="author.html#16742">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>AL13N skrev 21.6.2012 21:09:
&gt;<i> Op donderdag 21 juni 2012 19:01:51 schreef Claire Robinson:
</I>&gt;&gt;&gt;<i> since QA is waiting for a fix for this for a long time (pre-mga1), we
</I>&gt;&gt;&gt;<i> should get this fixed asap.
</I>&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;<i> PS: since we're enabling backports, we should make sure that the update
</I>&gt;&gt;&gt;<i> validation process would have one of both required tests for validation
</I>&gt;&gt;&gt;<i> with backports enabled and the other disabled.
</I>&gt;<i> [...]
</I>&gt;&gt;<i> It is doubled now because we have two releases and most updates include
</I>&gt;&gt;<i> both. It will be effectively quadrupled with this plan and that would be
</I>&gt;&gt;<i> unsustainable. We just don't have the manpower or enough hours in a day,
</I>&gt;&gt;<i> we are struggling to cope as it is.
</I>&gt;<i> [...]
</I>&gt;<i>
</I>&gt;<i> actually, it doesn't need to be.
</I>&gt;<i>
</I>&gt;<i> you already test twice before validating updates, right?
</I>&gt;<i>
</I>&gt;<i> so, there's 2 options:
</I>&gt;<i>
</I>&gt;<i> - testing i586 with backports enabled
</I>&gt;<i> - testing x86_64 without backports enabled
</I>&gt;<i>
</I>&gt;<i> this is still 2 tests, and this is sufficient.
</I>&gt;<i>
</I>
NO.

First of all, _anything_ heading for updates that is not noarch needs
to be validated on both arches.

Secondly, when QA validate stuff for /updates, they dont need
to test _anything_ against backports as /updates is _only_ used to
fix stuff in /release &amp; /updates.

If something in backports breaks as a result of something going to
/updates, that's a separate bug against backported package and will
be handled after.

Remember that /updates is priority 1, and /backports is handled
as QA time permits at lower priority.

--
Thomas
</PRE>









































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="016746.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
	<LI>Next message: <A HREF="016744.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16742">[ date ]</a>
              <a href="thread.html#16742">[ thread ]</a>
              <a href="subject.html#16742">[ subject ]</a>
              <a href="author.html#16742">[ 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>