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-May/015908.html | 87 +++++++++++++++++++++++++++++++++ 1 file changed, 87 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-May/015908.html (limited to 'zarb-ml/mageia-dev/2012-May/015908.html') diff --git a/zarb-ml/mageia-dev/2012-May/015908.html b/zarb-ml/mageia-dev/2012-May/015908.html new file mode 100644 index 000000000..89a3c5946 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-May/015908.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] Bugzilla mass ping + + + + + + + + + +

[Mageia-dev] Bugzilla mass ping

+ Olav Vitters + olav at vitters.nl +
+ Mon May 28 23:36:30 CEST 2012 +

+
+ +
On Sat, May 26, 2012 at 02:34:22PM +0200, Marja van Waes wrote:
+> On 26-05-12 13:23, Anne Nicolas wrote:
+> 
+> >
+> >Well rather than that it should be switched to Cauldron
+> >
+> 
+> According to https://wiki.mageia.org/en/Triage_guide#The_bug_affects_two_different_releases.21_What_now.3F
+> we should clone the still valid cauldron bugs for Mageia 2, and the
+> cauldron bug should then be set to block the same bug in Mageia 2.
+
+If filed before, I assume it'll of course affect Mageia 2. I prefer
+either setting version or target milestone to lowest Mageia version in
+which the bug should be fixed.
+
+Even when having two: We just branched, I prefer if all current bugs are
+assumed to be Mageia 2 ones with the Cauldron still not reported.
+
+-- 
+Regards,
+Olav
+
+ + + + + + + + + + + + + +
+

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