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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Release cycles proposals, and discussion
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycles%20proposals%2C%20and%20discussion&In-Reply-To=%3C4DFC5609.6060409%40laposte.net%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="005712.html">
<LINK REL="Next" HREF="005824.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Release cycles proposals, and discussion</H1>
<B>andre999</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycles%20proposals%2C%20and%20discussion&In-Reply-To=%3C4DFC5609.6060409%40laposte.net%3E"
TITLE="[Mageia-dev] Release cycles proposals, and discussion">andr55 at laposte.net
</A><BR>
<I>Sat Jun 18 09:38:49 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="005712.html">[Mageia-dev] Release cycles proposals, and discussion
</A></li>
<LI>Next message: <A HREF="005824.html">[Mageia-dev] Release cycles proposals, and discussion
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#5809">[ date ]</a>
<a href="thread.html#5809">[ thread ]</a>
<a href="subject.html#5809">[ subject ]</a>
<a href="author.html#5809">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Michael Scherer a écrit :
><i> Proposal 1:
</I>><i> 6 months release cycle -> 12 months life cycle
</I>><i> ( Fedora, Ubuntu, Mandriva< 2010.1&& Mandriva != 2006.0 )
</I>><i>
</I>><i> Proposal 2:
</I>><i> 9 months release cycle -> 18 months life cycle
</I>><i> ( ~ opensuse and the one we used for Mageia 1 )
</I>><i>
</I>><i> Proposal 3:
</I>><i> 12 months release cycle -> 24 months life cycle
</I>><i> ( Mandriva> 2010.1 )
</I>
First, suggest an amended freeze process (idea from recent report of another project)
Instead of a freeze on cauldron until everything is ready for the release, we do
1) short freeze on cauldron
2) copy cauldron to pre-release branch, which remains frozen until release
3) immediately unfreeze cauldron.
- we avoid blocking cauldron, while leaving pre-release frozen for bug fixes.
- updates can continue on cauldron. Bugfixes can be applied to newer versions, if present in
cauldron, at the same time as corresponding bugfixes in pre-release.
- activities like translation can continue in cauldron, meaning less rush for such updates.
- because cauldron is open to changes (virtually) all the time, they don't have to be put off and
perhaps forgotten.
- the cauldron cycle is extented by the time of the pre-release freeze. e.g. In a release cycle of
6 months and a pre-release freeze of 1 month, the cauldron cycle would be 7 months.
This allows more time to iron out the pre-release bugs and more time for cauldron.
- with the longer pre-release freeze, it may be appropriate to modify somewhat the policy on what
is accepted during freeze. (Certain more recent packages or translations, for example.)
- note that we would still have to monitor cauldron to avoid freezing partially implemented complex
changes, such as a major update of kde or gnome or perl, etc. But we have to do that now, anyway.
><i> Proposal 1 :
</I>><i> ---------------
</I>My personal preference
><i> Pros:
</I>><i> - better hardware support
</I>><i> - up to date versions / upstream projects (must have for developers)
</I>- coincides with kde/gnome releases
- amended freeze process (outlined above) would lengthen both pre-release freeze time and cauldron
development time.
A 1-month pre-release freeze would add 1 month to cauldron development time.
This would tend to alleviate the rush of the 6-month release cycle.
><i> - short life cycle
</I>would be alleviated by having periodic long term support releases (lasting at least 2 years).
><i> Proposal 2
</I>><i> ----------------
</I>><i> Pros:
</I>- amended freeze process outlined above would still be advantageous, to a lessor degree.
><i> Cons:
</I>><i> - not synchronized with gnome or others that use a 6 month cycle
</I>><i> - potentially release when there isn't much activity (like during Holidays)
</I>- release would not be the same month every year
e.g. 2011 june ; 2012 mar ; 2012 dec ; 2013 sep ; 2014 june ...
so users won't know when to expect a release
><i> Proposal 3 :
</I>><i> ------------
</I>Would prefer to avoid this.
Additional cons :
- periodic long-term support releases with a shorter release cycle would be more advantageous, in
terms of providing long-term stability for the few who would prefer it, while allowing a more
up-to-date distro.
- requires more updates and backports, in order to keep up to date with upstream, which doesn't
necessarily reduce workload over shorter release cycles.
my 2 cents :)
--
André
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="005712.html">[Mageia-dev] Release cycles proposals, and discussion
</A></li>
<LI>Next message: <A HREF="005824.html">[Mageia-dev] Release cycles proposals, and discussion
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#5809">[ date ]</a>
<a href="thread.html#5809">[ thread ]</a>
<a href="subject.html#5809">[ subject ]</a>
<a href="author.html#5809">[ 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>
|
