From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-June/006034.html | 108 +++++++++++++++++++++++++++++++ 1 file changed, 108 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-June/006034.html (limited to 'zarb-ml/mageia-dev/2011-June/006034.html') diff --git a/zarb-ml/mageia-dev/2011-June/006034.html b/zarb-ml/mageia-dev/2011-June/006034.html new file mode 100644 index 000000000..442b64ad7 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006034.html @@ -0,0 +1,108 @@ + + + + [Mageia-dev] Update of backport, policy proposal + + + + + + + + + +

[Mageia-dev] Update of backport, policy proposal

+ atilla ontas + tarakbumba at gmail.com +
+ Sun Jun 26 12:40:04 CEST 2011 +

+
+ +
2011/6/26 Daniel Kreuter <daniel.kreuter85 at googlemail.com>:
+> On Sun, Jun 26, 2011 at 10:58 AM, atilla ontas <tarakbumba at gmail.com> wrote:
+>>
+>> Look at Debian and Arch Linux who haven't any paid developers but
+>> community distros. Stable Debian releases provide software from a
+>> century ago for the sake of stability. Arch provides latest software
+>> including core system and occaionally have breakages. I think Mageia
+>> should be between two of them. Release latest software in updates for
+>> non core system and libs, keep core system stable. Remove this
+>> backports thingy.
+>>
+>> My 2 cents...
+>
+> This approach looks quite good, but the new software should be tested quite
+> good so the system will not break. Sure core system won't break with this
+> approach but what about the other software?
+>
+>
+>
+>
+I don't mean no need to test. Of course they should be placed in
+testing repo first.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1