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

[Mageia-dev] Backports policy proposal

+ Samuel Verschelde + stormi at laposte.net +
+ Tue Jun 28 14:43:35 CEST 2011 +

+
+ +
+Le vendredi 24 juin 2011 02:10:14, Michael Scherer a écrit :
+> I would also propose a few rules :
+> 
+> "a package should have been in cauldron since 1 week before being
+> backported", so we can at least ensure there was a minimal test on it,
+> Ie, if I package stuff-virtual-manager, I cannot backport it before 1
+> week. If we have a package of stuff-virtual-manager since 1 month, and
+> that I update a new version, then I can backport. The idea is that a
+> newer packages may suffer from more bug than older one.
+
+Could this apply only to "-backport" media and not "-backport_testing " media 
+? I would find good to be able to send a package very quickly to 
+backports_testing so that I can start to be tested as soon as possible. A 
+whole week for that would be a long time, considering that after that you have 
+to add more time so that the backport can be tested.
+
+By the way I think a packager usually knows the risks there is to send a 
+package too quickly to the backports and that we don't necessarily need to 
+enforce such a strict "1 week" rule. Especially when sending to 
+backports_testing first.
+
+ 
+> - cannot be backported if this is not a leaf package, will be revised
+> later
+
+I would like to be less strict, by replacing "leaf package" by "leaf group of 
+packages, tighly tied together by strict requires".
+
+Examples : 
+- A requires newer B and C, and no other package requires B and C (quite 
+common with games where data are split into separate packages) => you can 
+backport A, B, C. To me this situation should be possible.
+- A requires newer B, but D depends on B too => you can't backport A and B 
+alone, but if the maintainers consider it acceptable to enforce upgrade of D 
+when someone wants to upgrade A or upgrade of A when someone wants to upgrade 
+D (could be related pieces of software), then you can backport A, B and D (and 
+make sure to set the good requires). To me this situation would be nice to 
+have as an available option.
+
+Best regards
+
+Samuel Verschelde
+
+
+ + + + + + + + + + + + +
+

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