summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-June/005648.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2011-June/005648.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-1be510f9529cb082f802408b472a77d074b394c0.tar
archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz
archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2
archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz
archives-1be510f9529cb082f802408b472a77d074b394c0.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005648.html')
-rw-r--r--zarb-ml/mageia-dev/2011-June/005648.html170
1 files changed, 170 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005648.html b/zarb-ml/mageia-dev/2011-June/005648.html
new file mode 100644
index 000000000..59c4dd289
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-June/005648.html
@@ -0,0 +1,170 @@
+<!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=%3CBANLkTi%3D1FgekWhAZDpTYmW5DHvCQw01p2A%40mail.gmail.com%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="005580.html">
+ <LINK REL="Next" HREF="005649.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Release cycles proposals, and discussion</H1>
+ <B>Ahmad Samir</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycles%20proposals%2C%20and%20discussion&In-Reply-To=%3CBANLkTi%3D1FgekWhAZDpTYmW5DHvCQw01p2A%40mail.gmail.com%3E"
+ TITLE="[Mageia-dev] Release cycles proposals, and discussion">ahmadsamir3891 at gmail.com
+ </A><BR>
+ <I>Tue Jun 14 20:06:44 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="005580.html">[Mageia-dev] Release cycles proposals, and discussion
+</A></li>
+ <LI>Next message: <A HREF="005649.html">[Mageia-dev] Release cycles proposals, and discussion
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5648">[ date ]</a>
+ <a href="thread.html#5648">[ thread ]</a>
+ <a href="subject.html#5648">[ subject ]</a>
+ <a href="author.html#5648">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On 14 June 2011 09:25, Thorsten van Lil &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">tvl83 at gmx.de</A>&gt; wrote:
+[...]
+&gt;<i>
+</I>&gt;<i> Backports aren't supposed to be for the averaged user
+</I>
+I've seen this argument more than once in this thread. Why isn't
+backports suitable for the average user? that same average user would
+install an RPM package from a 3rd party repo or the official web site
+of an application in a heartbeat to get a new version of &quot;foo&quot;.
+
+The &quot;backports isn't supported&quot; argument means that if backporting a
+new package requires a lot of changes then it won't be done, e.g. a
+new version of vlc/wine/foo isn't a problem, and if something goes
+wrong with the package after a while another backport will be done &quot;if
+it's not too much hassle&quot; (e.g. vlc requires a newer ffmpeg to make
+some video codec work better but that new ffmpeg is known to break
+some other apps then it won't be done).
+
+Packagers don't backport packages they know won't work or are crashy....
+
+&gt;<i> and shouldn't be used
+</I>&gt;<i> to bring the half of your system up to date.
+</I>
+The word &quot;stable release&quot; implies &quot;doesn't change much&quot;; so a new
+version of vlc or wine isn't a problem, but don't put &quot;updating to
+GNOME3 or KDE 4.8 in Mageia 1&quot; and &quot;stable&quot; in the same sentence, they
+don't fit..... such _huge_ changes need to happen in a development
+release so that the niggles (which are bound to show up) can be ironed
+out so that the distro becomes &quot;stable&quot; and ready to be released
+(Mageia 2).
+
+[...]
+
+--
+Ahmad Samir
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="005580.html">[Mageia-dev] Release cycles proposals, and discussion
+</A></li>
+ <LI>Next message: <A HREF="005649.html">[Mageia-dev] Release cycles proposals, and discussion
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#5648">[ date ]</a>
+ <a href="thread.html#5648">[ thread ]</a>
+ <a href="subject.html#5648">[ subject ]</a>
+ <a href="author.html#5648">[ 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>