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/006024.html | 114 +++++++++++++++++++++++++++++++ 1 file changed, 114 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-June/006024.html (limited to 'zarb-ml/mageia-dev/2011-June/006024.html') diff --git a/zarb-ml/mageia-dev/2011-June/006024.html b/zarb-ml/mageia-dev/2011-June/006024.html new file mode 100644 index 000000000..5e1ca497f --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006024.html @@ -0,0 +1,114 @@ + + + + [Mageia-dev] Update of backport, policy proposal + + + + + + + + + +

[Mageia-dev] Update of backport, policy proposal

+ Wolfgang Bornath + molch.b at googlemail.com +
+ Sun Jun 26 09:56:12 CEST 2011 +

+
+ +
A short reality check from userside:
+
+If foo-1.0 is in Mageia 1 and foo-1.1 is released upstream
+ - foo-1.1 will likely be integrated in Cauldron very soon after
+ - users will request to have foo-1.1 in Mageia 1
+ - if Mageia will not provide it then there will soon be local
+repositories where local packagers will do a "backport" for their
+friends.
+
+This may not be what Mageia backport policy will allow but we can not
+avoid people doing and using this, no matter how many warning signs we
+will publish. This has to be taken into account here.
+
+When a policy is found it has to be communicated very well, especially
+if that policy means that the user can not have foo-1.1 in his stable
+Mageia 1.
+
+This is important because former Mandriva users were used to get
+almost all new versions backported, if not officially then in 3rd
+party repos like MIB or MUD.
+
+-- 
+wobo
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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