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

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

+ David W. Hodgins + davidwhodgins at gmail.com +
+ Tue Jun 12 20:07:06 CEST 2012 +

+
+ +
On Fri, 08 Jun 2012 04:38:06 -0400, Samuel Verschelde <stormi at laposte.net> wrote:
+
+> I re-read the backports policy, and there's a part I think needs to be pointed
+> out before people start to backport packages.
+
+I have a different question.
+
+Will repositories such as "Core Backports" ever actually be used?
+
+If we follow the procedures used for normal updates, a backport will first
+be submitted to "Core Backports Testing", then assigned to qa.  Once
+validated, the backport srpm will be pushed to "Core Backports Updates".
+
+When would "Core Backports" ever be used?
+
+Regards, Dave Hodgins
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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