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
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] FireFox ESR <= we should totally go for this wrt 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%20FireFox%20ESR%20%3C%3D%20we%20should%20totally%20go%20for%20this%20wrt%0A%09stable%20releases&In-Reply-To=%3C201201132358.16603.alien%40rmail.be%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="011351.html">
<LINK REL="Next" HREF="011354.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] FireFox ESR <= we should totally go for this wrt stable releases</H1>
<B>Maarten Vanraes</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20FireFox%20ESR%20%3C%3D%20we%20should%20totally%20go%20for%20this%20wrt%0A%09stable%20releases&In-Reply-To=%3C201201132358.16603.alien%40rmail.be%3E"
TITLE="[Mageia-dev] FireFox ESR <= we should totally go for this wrt stable releases">alien at rmail.be
</A><BR>
<I>Fri Jan 13 23:58:16 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="011351.html">[Mageia-dev] FireFox ESR <= we should totally go for this wrt stable releases
</A></li>
<LI>Next message: <A HREF="011354.html">[Mageia-dev] FireFox ESR <= we should totally go for this wrt stable releases
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11352">[ date ]</a>
<a href="thread.html#11352">[ thread ]</a>
<a href="subject.html#11352">[ subject ]</a>
<a href="author.html#11352">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op vrijdag 13 januari 2012 23:10:53 schreef Jeff Robins:
><i> On Fri, Jan 13, 2012 at 1:20 PM, Maarten Vanraes <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">alien at rmail.be</A>> wrote:
</I>><i> > Op vrijdag 13 januari 2012 20:59:19 schreef Jeff Robins:
</I>><i> > > On Fri, Jan 13, 2012 at 6:00 AM, andre999 <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">andre999mga at laposte.net</A>>
</I>><i> >
</I>><i> > wrote:
</I>><i> > > > Wait.
</I>><i> > > > A long-term release version is kept updated for bugs, particularly
</I>><i> > > > security bugs, but doesn't add new features.
</I>><i> > > > Since it doesn't add new features, it is less likely to introduce new
</I>><i> > > > bugs, and so would be more secure.
</I>><i> > > > (That is why, in case you haven't noticed, that Firefox has more
</I>><i> >
</I>><i> > security
</I>><i> >
</I>><i> > > > issues than Seamonkey, which is one step behind Firefox in adopting
</I>><i> > > > new features.)
</I>><i> > > >
</I>><i> > > > So if you want a stable, secure browser, prefer among Mozilla
</I>><i> > > > browsers the Firefox long-term release, or for more stable,
</I>><i> > > > Seamonkey.
</I>><i> > > >
</I>><i> > > > For the minority of users who want the latest features, despite the
</I>><i> > > > greater risk, like the cauldron of Mozilla, it is easy to download
</I>><i> > > > the latest Firefox release, direct from upstream. (It will be
</I>><i> > > > available there at least a week sooner.)
</I>><i> > > > Upstream Firefox by default warns when the latest update is
</I>><i> > > > available.
</I>><i> > > >
</I>><i> > > > --
</I>><i> > > > André
</I>><i> > >
</I>><i> > > I think André is entirely correct and the ESR should meet the
</I>><i> >
</I>><i> > requirements
</I>><i> >
</I>><i> > > for a long-term Mageia. The ESR will get all of the security updates,
</I>><i> >
</I>><i> > but
</I>><i> >
</I>><i> > > not the new features so any argument about needing the latest to stay
</I>><i> > > secure is invalid. (
</I>><i> >
</I>><i> > <A HREF="http://www.anandtech.com/show/5378/mozilla-announces-firefox-extended-sup">http://www.anandtech.com/show/5378/mozilla-announces-firefox-extended-sup</A>
</I>><i> > po
</I>><i> >
</I>><i> > > rt-release )
</I>><i> > >
</I>><i> > > Also, the next upstream will be moving to quiet updates, unless Firefox
</I>><i> > > hasn't been restarted in the last 12 hours. So, users that want the
</I>><i> >
</I>><i> > latest
</I>><i> >
</I>><i> > > can use the upstream and be automatically updated.
</I>><i> > > (
</I>><i> >
</I>><i> > <A HREF="http://letsbytecode.com/general/10-firefox-will-be-updated-on-the-quiet/">http://letsbytecode.com/general/10-firefox-will-be-updated-on-the-quiet/</A>)
</I>><i> >
</I>><i> > > My only concern is the difference in release times. Mageia's is
</I>><i> > > 9months and Mozilla is 1year. Nine months from Mageia's 1st long-term
</I>><i> > > release, Mozilla will still be on the same FF, and will update FF in
</I>><i> > > the middle of the second Mageia long-term release. This would create
</I>><i> > > more work and a long-term Mageia, which will have a major component
</I>><i> > > update during the long-term support period.
</I>><i> > >
</I>><i> > > --Jeff
</I>><i> >
</I>><i> > look at the picture for the support period, the 1y warranteed versions
</I>><i> > cross
</I>><i> > over for 2 or 3 months
</I>><i> >
</I>><i> > so it's going to fit for as long as we have 9m release schedule
</I>><i>
</I>><i> The 2-3 month overlap doesn't solve our problem. Assuming that we both
</I>><i> start on the same month of the same year, which we aren't, and call it
</I>><i> January 2012:
</I>><i>
</I>><i> Jan 2012 (good):
</I>><i> We do long-term 1 and Mozilla does ESR1.
</I>><i>
</I>><i> Sept 2012(good):
</I>><i> We do long-term 2 and Mozilla has just released FF ESR2.
</I>><i>
</I>><i> June 2013(bad):
</I>><i> We do long-term 3, but Mozilla won't release FF ESR3 until Sept 2013. FF
</I>><i> ESR2 is defunct as of Jan 2013. We only get 3 months of support on ESR2 for
</I>><i> long-term 3.
</I>><i>
</I>><i> March 2014(good):
</I>><i> We do long-term 4 and Mozilla released FF ESR3 in Sept. We get support
</I>><i> until Dec 2015, which is when we release long-term 5.
</I>><i>
</I>><i> --Jeff
</I>
"your logic is flawed"
we have version freeze and testing several months before release
so, let's say mga2 ships with FF10.
if mga2 is release june, mga3 would be march 2013, with FF17.
mga4 would be released around dec 2013, with FF24
mga5 would be released with FF33, etc..
HOWEVER!
mga1 continues support until at least release of mga3, and thus will also
carry FF10.
mga2 has the same thing, when FF10 becomes EOL, mga2 will have to "update" to
FF17 as well... AND in advance of release of the new versions.
but otoh, this is all speculation on the continuation of 9m release schedule,
and if it's strictly adhered or not, and if FF isn't going to deviate or
change...
this is well enough in advance thinking imho, no need to think further than
this.
first we should also note if WE ourselves need to have LTS versions and IF we
can support that... etc...
in short, due to 3month overlap, the FF ERS cycle is 9m, just like mageia...
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="011351.html">[Mageia-dev] FireFox ESR <= we should totally go for this wrt stable releases
</A></li>
<LI>Next message: <A HREF="011354.html">[Mageia-dev] FireFox ESR <= we should totally go for this wrt stable releases
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11352">[ date ]</a>
<a href="thread.html#11352">[ thread ]</a>
<a href="subject.html#11352">[ subject ]</a>
<a href="author.html#11352">[ 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>
|
