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/016430.html | 140 +++++++++++++++++++++++++++++++ 1 file changed, 140 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-June/016430.html (limited to 'zarb-ml/mageia-dev/2012-June/016430.html') diff --git a/zarb-ml/mageia-dev/2012-June/016430.html b/zarb-ml/mageia-dev/2012-June/016430.html new file mode 100644 index 000000000..940a4a67e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016430.html @@ -0,0 +1,140 @@ + + + + [Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2 + + + + + + + + + +

[Mageia-dev] QA process for GNOME 3.4.2 for Mageia 2

+ Thomas Backlund + tmb at mageia.org +
+ Tue Jun 12 13:08:32 CEST 2012 +

+
+ +
12.06.2012 14:01, Olav Vitters skrev:
+> For Mageia 2, I'd like to:
+> - get my act together and fix a bunch of bugs (a lot of wrong
+>    suggests/requires, resulting in bugs&crashers)
+> - provide GNOME 3.4.2 as update
+>
+> But this concerns loads and loads of packages.
+>
+> How to best proceed?
+>
+> I saw mentioning that QA is really busy. How can I make this as simple
+> as possible for QA (not for myself)?
+>
+> Should I:
+
+[...]
+
+> #2 :
+>    - do everything in one go (combine 3.4.2 update with the bugfixes)?
+
+I'd say this is the most sane way as it means testing the packages in 
+one go (and also matches how KDE has been upgraded)
+
+
+#1 and #3 will mean more work for QA.
+
+--
+Thomas
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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