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-December/010221.html | 106 +++++++++++++++++++++++++++ 1 file changed, 106 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-December/010221.html (limited to 'zarb-ml/mageia-dev/2011-December/010221.html') diff --git a/zarb-ml/mageia-dev/2011-December/010221.html b/zarb-ml/mageia-dev/2011-December/010221.html new file mode 100644 index 000000000..a6ab54afc --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010221.html @@ -0,0 +1,106 @@ + + + + [Mageia-dev] RFC: Opening Backports (once again...) + + + + + + + + + +

[Mageia-dev] RFC: Opening Backports (once again...)

+ Samuel Verschelde + stormi at laposte.net +
+ Tue Dec 6 09:48:37 CET 2011 +

+
+ +
Le mardi 6 décembre 2011 00:29:03, Anssi Hannula a écrit :
+> > Using a separate branch is also a cleaner way of providing
+> > backports, and makes it easy to separate changes needed only
+> > for Cauldron (or backports).
+> 
+> Hm, how does this help with enabling backports (i.e. compared to simply
+> using cauldron repo)?
+
+The current system needs a rework to be able to accept packages submitted from 
+cauldron to 1/backports_testing while forbidding submit from cauldron to 
+1/updates_testing
+
+Back in september I had proposed 2 solutions :
+- the current proposal from tmb, which I support (but which requires a change 
+in the policy as it is currently defined)
+- allowing to submit anywhere from cauldron (and have QA verify that the 
+packages have been submitted from the right branch, and burn publicly 
+packagers who submit from cauldron to updates_testing)
+
+Both would require little tweaking to the build system.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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