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

[Mageia-dev] Bugzilla mass ping

+ Marja van Waes + marja11 at xs4all.nl +
+ Sat May 26 17:01:41 CEST 2012 +

+
+ +
On 26-05-12 14:52, nicolas vigier wrote:
+> On Sat, 26 May 2012, 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.
+>
+> That's a lot of bugs to clone. Instead of cloning every bugs, I would
+> rather set bugs to Cauldron, and when someone fix a cauldron bug he
+> should decide whether it's something worth fixing in Mageia 2 or not,
+> and open a Mageia 2 bug if necessary.
+>
+
+AL13N suggested to set a ALSO_MGA2 keyword for those bugs (so leave them 
+to cauldron) instead of cloning them.
+
+We don't have such a keyword atm, but I'll use MGA2TOO on the whiteboard 
+instead for now.
+
+That might change, depending on what leuhmanu, remmy and other bug squad 
+members think about it. They might have an even better idea :)
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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