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/2012-June/016296.html | 119 +++++++++++++++++++++++++++++++ 1 file changed, 119 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-June/016296.html (limited to 'zarb-ml/mageia-dev/2012-June/016296.html') diff --git a/zarb-ml/mageia-dev/2012-June/016296.html b/zarb-ml/mageia-dev/2012-June/016296.html new file mode 100644 index 000000000..2c6f82dd4 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016296.html @@ -0,0 +1,119 @@ + + + + [Mageia-dev] Backports policy clarification (and discussion) + + + + + + + + + +

[Mageia-dev] Backports policy clarification (and discussion)

+ Samuel Verschelde + stormi at laposte.net +
+ Fri Jun 8 19:57:45 CEST 2012 +

+
+ +
Le vendredi 8 juin 2012 16:45:28, Angelo Naselli a écrit :
+> venerdì 8 giugno 2012 alle 16:22, Samuel Verschelde ha scritto:
+> > I think you missed my point. If Mageia 1 "backports" has higher versions
+> > than Mageia 2 "release" (not backports), upgrade can fail because
+> > currently our tools do not take backports from the target release
+> > (mageia 2) into account when upgrading a distro.
+> 
+> And i think a mga N-1 bp should have mga N bp as well in that case or
+> should follow the same rules as between cauldron and updates e.g 1.1mgaN-1
+> means 2mgaN. Who backports will care, some more work does not mean we
+> can't have backports, just that we do really want that backport :)
+> 
+> What we need is, however, being sure no one submits a package to bp_testing
+> (as well as to update_testing) without asking to package maintaner or
+> adding a bug report to manage that update/backport. I say that because it
+> happened for updates. I think it should be clear that QA won't test a
+> package only because it is in XX_testing repository and that maintainer
+> does not have to go and see on testing to know that someone has already
+> done the work, maybe after having done some work on it... am i wrong?
+> 
+
+Yes, it is already clear in the policy as it is written, in my opinion.
+
+Samuel
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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