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

[Mageia-dev] Backports policy proposal

+ Maarten Vanraes + maarten.vanraes at gmail.com +
+ Fri Jun 24 08:30:15 CEST 2011 +

+
+ +
Op vrijdag 24 juni 2011 02:10:14 schreef Michael Scherer:
+[...]
+> 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.
+[..]
+
+This seems hard to enforce... i can imagine if you make backport, it has 
+essentially the same version as in cauldron, i can think that there is a few 
+spec file changes that are only for backports, and thus the release becomes 
+newer than the one in cauldron
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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