diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-February/011843.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-February/011843.html | 99 |
1 files changed, 99 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-February/011843.html b/zarb-ml/mageia-dev/2012-February/011843.html new file mode 100644 index 000000000..089e21281 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-February/011843.html @@ -0,0 +1,99 @@ +<!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%20stable%20releases&In-Reply-To=%3C4F352675.2060907%40arcor.de%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="011834.html"> + <LINK REL="Next" HREF="011844.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] FireFox ESR <= we should totally go for this wrt stable releases</H1> + <B>Florian Hubold</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%20stable%20releases&In-Reply-To=%3C4F352675.2060907%40arcor.de%3E" + TITLE="[Mageia-dev] FireFox ESR <= we should totally go for this wrt stable releases">doktor5000 at arcor.de + </A><BR> + <I>Fri Feb 10 15:15:17 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="011834.html">[Mageia-dev] FireFox ESR <= we should totally go for this wrt stable releases +</A></li> + <LI>Next message: <A HREF="011844.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#11843">[ date ]</a> + <a href="thread.html#11843">[ thread ]</a> + <a href="subject.html#11843">[ subject ]</a> + <a href="author.html#11843">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Am 09.02.2012 21:56, schrieb Maarten Vanraes: +><i> Op donderdag 09 februari 2012 13:04:00 schreef Sander Lepik: +</I>>><i> 09.02.2012 13:35, AL13N kirjutas: +</I>>>><i> ihmo, the users who want the latest versions will not even wait one week, +</I>>>><i> and will grab them from upstream. If we really wanted the latest release, +</I>>>><i> someone could backport them. +</I>>><i> And backports work since what time? +</I>><i> that is irrelevant, and we should not assume it will not be ready. +</I>><i> +</I>>>><i> the end users will benefit too, because the modules/plugins will still +</I>>>><i> work and not being unstable at every update. as a long time stable user, +</I>>>><i> i prefer the ESR... we've been complaining about too short +</I>>>><i> releasecycles... this is the answer, we should use it. +</I>>><i> Most users don't know what to do with tarball. They only know that their +</I>>><i> browser doesn't have latest promoted changes. And that means +</I>>><i> distribution is doing something wrong for them. +</I>>><i> +</I>>><i> We were complaining because extensions didn't work. I don't know how +</I>>><i> many plugins there were with problems. Can't remember any myself. +</I>>><i> Nonbinary extensions are now compatible by default, so one problem less. +</I>>><i> +</I>>><i> ESR means QA testing anyway. It's only bugfixes but that doesn't mean +</I>>><i> you can update w/o testing. +</I>><i> iinm our update policy dictates that our updates should only have updates in +</I>><i> it, and no new features... (unless there is no such supported version) +</I>Our update policy already has an exception for Firefox, and so far there were +no bigger issues during updates from our initial 4.0 to 10.0. And if most other +distros don't use ESR, we're kind of alienated, and users will ask why we do that, +because we're not aimed at enterprise usage currently. + +><i> +</I>><i> well, now there is... Either the new versions with extra features go into +</I>><i> backports, or not at all. if this becomes a problem, then it's one more reason +</I>><i> to fix the backports. +</I>><i> +</I>><i> we have a clear policy, we should follow it. +</I>Hypothetically, it would be kinda useless to have two versions of our default +browser, +meaning twice the QA and support, and backports are surely not opened solely +for firefox. +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="011834.html">[Mageia-dev] FireFox ESR <= we should totally go for this wrt stable releases +</A></li> + <LI>Next message: <A HREF="011844.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#11843">[ date ]</a> + <a href="thread.html#11843">[ thread ]</a> + <a href="subject.html#11843">[ subject ]</a> + <a href="author.html#11843">[ 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> |