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

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

+ Samuel Verschelde + stormi at laposte.net +
+ Fri Jun 8 13:39:07 CEST 2012 +

+
+ +
Le vendredi 8 juin 2012 13:31:30, Angelo Naselli a écrit :
+> > If there is security issue then you have to fix it on cauldron too
+> > (usually with new version, so you can backport it to stable version). At
+> > least before release. And after backports are closed you can upgrade to
+> > latest stable version (for example mga3) and get patched version this
+> > way. I don't see the problem here.
+> 
+> Well I can't see how we can close a bp since we say we give 9 months of
+> supporting version. If we support bp, we also need to provides fixing at
+> least. But i got your point, it's a kind o release freeze for bp for the
+> mga n-2.
+> 
+
+We support each release 18 month at least (that is, unless we manage to do 
+more in the future), so his proposal means stopping backports support too 
+early.
+
+Samuel
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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