summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-July/007108.html
blob: becd70668c0146658d564db3c81b974645f1ee90 (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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Updates and 0 release
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Updates%20and%200%20release&In-Reply-To=%3C4E327183.50808%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="007107.html">
   <LINK REL="Next"  HREF="007119.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Updates and 0 release</H1>
    <B>Colin Guthrie</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Updates%20and%200%20release&In-Reply-To=%3C4E327183.50808%40colin.guthr.ie%3E"
       TITLE="[Mageia-dev] Updates and 0 release">mageia at colin.guthr.ie
       </A><BR>
    <I>Fri Jul 29 10:38:27 CEST 2011</I>
    <P><UL>
        <LI>Previous message: <A HREF="007107.html">[Mageia-dev] Updates and 0 release
</A></li>
        <LI>Next message: <A HREF="007119.html">[Mageia-dev] Updates and 0 release
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#7108">[ date ]</a>
              <a href="thread.html#7108">[ thread ]</a>
              <a href="subject.html#7108">[ subject ]</a>
              <a href="author.html#7108">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>'Twas brillig, and Samuel Verschelde at 29/07/11 09:32 did gyre and gimble:
&gt;<i> Le vendredi 29 juillet 2011 10:25:02, Colin Guthrie a &#233;crit :
</I>&gt;&gt;<i> 'Twas brillig, and Samuel Verschelde at 28/07/11 13:11 did gyre and gimble:
</I>&gt;&gt;&gt;<i> Le jeudi 28 juillet 2011 13:02:26, Colin Guthrie a &#233;crit :
</I>&gt;&gt;&gt;&gt;<i> 'Twas brillig, and Samuel Verschelde at 28/07/11 09:08 did gyre and 
</I>&gt;<i> gimble:
</I>&gt;&gt;&gt;&gt;&gt;<i> We have updates blocked by this release 0 issue, so we need a quick
</I>&gt;&gt;&gt;&gt;&gt;<i> decision. I propose that if tomorrow nobody reacted against the
</I>&gt;&gt;&gt;&gt;&gt;<i> proposal, it will be adopted.
</I>&gt;&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;&gt;<i> Personally, I would vote to keep it the way it is with the 0 releases.
</I>&gt;&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;&gt;<i> I'm not convinced that any of the arguments represent real world
</I>&gt;&gt;&gt;&gt;<i> problems.
</I>&gt;&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;&gt;<i> Col
</I>&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;<i> Here is a question I got yesterday, which the proposal solves, but that's
</I>&gt;&gt;&gt;<i> not a very common issue and maybe the 0 releases way works with it too :
</I>&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;<i> If we had imported it before mageia 1 was released, we would have had
</I>&gt;&gt;&gt;<i> cultivation-9-0.20071217.6.mga1 in mageia 1 (a pre-release).
</I>&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;<i> Then suppose we want to update it to the final 9 release in both cauldron
</I>&gt;&gt;&gt;<i> and mageia 1 : we have cultivation-9-1.mga1 in cauldron. But what
</I>&gt;&gt;&gt;<i> release should we use in updates for mageia 1 ?
</I>&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;<i> cultivation-9-0.1.mga1 doesn't work because cultivation-9-0.1.mga1 &lt;
</I>&gt;&gt;&gt;<i> cultivation-9-0.20071217.6.mga1
</I>&gt;&gt;&gt;<i>
</I>&gt;&gt;&gt;<i> Is there a way to do it right with a 0 release ?
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> Yeah, I concede that this particular scenario would cause problems :s
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> Fair point, well made :D
</I>&gt;<i> 
</I>&gt;<i> Does it mean that you agree with the proposal ? Not that I badly want it to be 
</I>&gt;<i> adopted, but I really would like to unlock the current updates in the pipe :)
</I>
If it helps speed the process, then sure, I will add my official support
for an amendment to the policy as per misc's original mail (I don't
think my opinion carries that much weight tho'! :p)

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="007107.html">[Mageia-dev] Updates and 0 release
</A></li>
	<LI>Next message: <A HREF="007119.html">[Mageia-dev] Updates and 0 release
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#7108">[ date ]</a>
              <a href="thread.html#7108">[ thread ]</a>
              <a href="subject.html#7108">[ subject ]</a>
              <a href="author.html#7108">[ 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>