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

[Mageia-dev] Bugzilla mass ping

+ blind Pete + 0123peter at gmail.com +
+ Wed May 30 04:14:48 CEST 2012 +

+
+ +
nicolas vigier wrote:
+
+[snip]
+
+> The way I see it, the bug should be fixed first in Cauldron, because
+> it's the developement version. And when it is confirmed that the fix is
+> good, it is applied to all affected stable versions.
+
+That would depend on whether the bug was an annoyance or a 
+show stopping urgent security fix.  
+
+[snip]
+
+> I think spamming people with multiple bugs for the same issue only
+> increase the chances of people ignoring bugzilla emails.
+> 
+> It also makes it difficult to read all infos about the bugs, some infos
+> will be in the bug for Mageia 2, other infos will be in the Cauldron
+> bug.
+> 
+> In my opinion we should have only one bug for an issue, with keyword or
+> comments to indicate that it also affect other versions. And only when a
+> solution is found, the bug is forked for each release to track the
+> upload and QA tests.
+
+Would it be possible to have a bug report refer to multiple versions 
+and simultaneously have X marked as OLD, Y marked as FIXED, and 
+Z marked as BLOCKING?  
+
+-- 
+blind Pete
+Sig goes here...  
+
+
+ + + + + +
+

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