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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Subrel for version updates on stable releases
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Subrel%20for%20version%20updates%20on%20stable%20releases&In-Reply-To=%3C4EAAD58E.20900%40mageia.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="009177.html">
<LINK REL="Next" HREF="009183.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Subrel for version updates on stable releases</H1>
<B>Anssi Hannula</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Subrel%20for%20version%20updates%20on%20stable%20releases&In-Reply-To=%3C4EAAD58E.20900%40mageia.org%3E"
TITLE="[Mageia-dev] Subrel for version updates on stable releases">anssi at mageia.org
</A><BR>
<I>Fri Oct 28 18:17:18 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="009177.html">[Mageia-dev] [changelog] [RPM] cauldron core/release perl-SOAP-Lite-0.714.0-1.mga2
</A></li>
<LI>Next message: <A HREF="009183.html">[Mageia-dev] Subrel for version updates on stable releases
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9179">[ date ]</a>
<a href="thread.html#9179">[ thread ]</a>
<a href="subject.html#9179">[ subject ]</a>
<a href="author.html#9179">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Hi!
Currently the updates policy [1] says that updates to a new version
should have 1.1.mga1 as release, and that cauldron should be bumped to
2.mga2 on those cases.
However, on the packages where version updates are done (e.g. wine,
flash-player-plugin, opera, firefox, chromium), doing that causes the
following chain of events on every update:
1. cauldron submission with 1.mga2
2. mga1 submission with 1.1.mga1
3. cauldron submission with 2.mga2
So the pkgs have to always be submitted to cauldron twice (unless one
skips right to 2.mga2, which would be rather confusing IMO).
I suggest we change the policy to say that package updates to stable
should use 1.mga1 release (i.e. no subrel), so that it goes:
1. cauldron submission with 1.mga2
2. mga1 submission with 1.mga1
and no extra submissions or commits required.
Then, if some extra fix is needed, one does:
1. cauldron submission with 2.mga2
2. mga1 submission with 1.1.mga1
WDYT?
[1] <A HREF="http://www.mageia.org/wiki/doku.php?id=updates_policy">http://www.mageia.org/wiki/doku.php?id=updates_policy</A>
--
Anssi Hannula
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="009177.html">[Mageia-dev] [changelog] [RPM] cauldron core/release perl-SOAP-Lite-0.714.0-1.mga2
</A></li>
<LI>Next message: <A HREF="009183.html">[Mageia-dev] Subrel for version updates on stable releases
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9179">[ date ]</a>
<a href="thread.html#9179">[ thread ]</a>
<a href="subject.html#9179">[ subject ]</a>
<a href="author.html#9179">[ 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>
|
