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/006045.html | 96 ++++++++++++++++++++++++++++++++ 1 file changed, 96 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-June/006045.html (limited to 'zarb-ml/mageia-dev/2011-June/006045.html') diff --git a/zarb-ml/mageia-dev/2011-June/006045.html b/zarb-ml/mageia-dev/2011-June/006045.html new file mode 100644 index 000000000..80974c137 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006045.html @@ -0,0 +1,96 @@ + + + + [Mageia-dev] Backports policy proposal + + + + + + + + + +

[Mageia-dev] Backports policy proposal

+ Anssi Hannula + anssi.hannula at iki.fi +
+ Sun Jun 26 17:00:06 CEST 2011 +

+
+ +
On 26.06.2011 01:34, Michael Scherer wrote:
+> Le vendredi 24 juin 2011 à 17:33 +0300, Anssi Hannula a écrit :
+>> On 24.06.2011 03:10, Michael Scherer wrote:
+>>> Another rule that we could add is that cauldron should always be newer
+>>> than backports, in order to ensure upgradability. The same goes for n-2
+>>> and n-1 release.
+>>> While this seems innocent, do not forget this will have a impact when we
+>>> do the version freeze.
+>>
+>> So this will prevent backporting anything to mga1 if it is not in mga2
+>> release/updates ?
+> 
+> That's a good question but yes, I would consider such policy.
+> Ie, do backport only for the latest supported release.
+
+This will essentially prevent backporting anything to mga1 after mga2
+release. :/
+
+-- 
+Anssi Hannula
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

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