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

[Mageia-dev] Update of backport, policy proposal

+ Michael Scherer + misc at zarb.org +
+ Sun Jun 26 11:38:46 CEST 2011 +

+
+ +
Le dimanche 26 juin 2011 à 11:49 +0300, Sander Lepik a écrit :
+> 24.06.2011 03:15, Michael Scherer kirjutas:
+> > Hi,
+> >
+> > [ ... ]
+> >
+> > Last solution, declare that cherry picking is not supported, or that
+> > people are on their own, and explain the reason. However, people have
+> > been asking this, and recommend this. This would also be against a goal
+> > of having confidence in the backports.
+> >
+> >
+> > Again, and as said in the title, this is a proposal so feel free to
+> > comment.
+> >
+> Reading comments here and knowing that our QA team is in trouble already - i don't see how 
+> would QA handle backports. I can also see that there might come time when backports are 
+> unpatched and thus unsecure.
+
+At what point is QA team mentioned in the process ( which is in another
+thread ) ?
+
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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