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

[Mageia-dev] Backports policy proposal

+ Michael Scherer + misc at zarb.org +
+ Sun Jun 26 00:34:41 CEST 2011 +

+
+ +
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.
+
+> Also, I don't see the advantage in preventing backports during freeze.
+> The backports are re-allowed soon anyway, and the upgradeability goes
+> away anyway.
+
+Then if people use mgaonline, it will fail, and then, people will start
+to say "we cannot upgrade distribution" and sooner or later, mgaonline
+will have the same bad reputation that backports had.
+
+
+So either we want mgaonline to be rock solid ( and I think that would be
+a benefit, and that if we managed to do it for mandriva, we can continue
+), or we want to offer backports that will disrupt it, and thus have "if
+you use backport, upgrade will not be supported", which is yet another
+reason for people to not use it.
+
+I do not see how we could win on both, except by limiting backporting to
+make sure system are still upgradable.
+
+Another solution would be some smart upgrader that do enable backports
+for upgrade, without taking everything. And until we see a working piece
+of code doing that, this will not be a solution.
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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