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/20110207/002478.html | 80 +++++++++++++++++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110207/002478.html (limited to 'zarb-ml/mageia-dev/20110207/002478.html') diff --git a/zarb-ml/mageia-dev/20110207/002478.html b/zarb-ml/mageia-dev/20110207/002478.html new file mode 100644 index 000000000..c131bb233 --- /dev/null +++ b/zarb-ml/mageia-dev/20110207/002478.html @@ -0,0 +1,80 @@ + + + + [Mageia-dev] New mockups about mageia-app-db + + + + + + + + + +

[Mageia-dev] New mockups about mageia-app-db

+ Michael Scherer + misc at zarb.org +
+ Mon Feb 7 18:02:28 CET 2011 +

+
+ +
Le lundi 07 février 2011 à 00:17 +0100, Fabrice Facorat a écrit :
+> 2011/2/6 Marcello Anni <marcello.anni at alice.it>:
+> >
+> > also here, i mean something like this: "Mageia 2011" and "Mageia 2012"
+> 
+> this won't scale when you will have more and more release, except if
+> you plan to show only 2 releases, and so to support a mandriva release
+> only during 2 releases cycles.
+
+Technically, that not mandriva, but mageia :)
+
+And since one of the goal of the tool is to manage people who ask for
+backports, as said on http://mageia-app-db.tuxette.fr/projects/1/wiki ,
+it make sense to limit this to supported releases. 
+
+>From a ressource point of view, I do not think it would be wise to keep
+everything ( ie, to still keep stuff server side to change all
+releases ). And limiting the releases supported on every tools we use
+would also remove clutter on various part of the interface ( ie bugzilla
+among others, or forums ).
+
+So yes, just show only X releases by default make perfect sense, IMHO
+-- 
+Michael Scherer
+
+
+ + +
+

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