<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Bugzilla mass ping
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Bugzilla%20mass%20ping&In-Reply-To=%3Codcg99-712.ln1%40psd.motzarella.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="015929.html">
<LINK REL="Next" HREF="015951.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Bugzilla mass ping</H1>
<B>blind Pete</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Bugzilla%20mass%20ping&In-Reply-To=%3Codcg99-712.ln1%40psd.motzarella.org%3E"
TITLE="[Mageia-dev] Bugzilla mass ping">0123peter at gmail.com
</A><BR>
<I>Wed May 30 04:14:48 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="015929.html">[Mageia-dev] Bugzilla mass ping
</A></li>
<LI>Next message: <A HREF="015951.html">[Mageia-dev] Bugzilla mass ping
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#15948">[ date ]</a>
<a href="thread.html#15948">[ thread ]</a>
<a href="subject.html#15948">[ subject ]</a>
<a href="author.html#15948">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>nicolas vigier wrote:
[snip]
><i> The way I see it, the bug should be fixed first in Cauldron, because
</I>><i> it's the developement version. And when it is confirmed that the fix is
</I>><i> good, it is applied to all affected stable versions.
</I>
That would depend on whether the bug was an annoyance or a
show stopping urgent security fix.
[snip]
><i> I think spamming people with multiple bugs for the same issue only
</I>><i> increase the chances of people ignoring bugzilla emails.
</I>><i>
</I>><i> It also makes it difficult to read all infos about the bugs, some infos
</I>><i> will be in the bug for Mageia 2, other infos will be in the Cauldron
</I>><i> bug.
</I>><i>
</I>><i> In my opinion we should have only one bug for an issue, with keyword or
</I>><i> comments to indicate that it also affect other versions. And only when a
</I>><i> solution is found, the bug is forked for each release to track the
</I>><i> upload and QA tests.
</I>
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...
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="015929.html">[Mageia-dev] Bugzilla mass ping
</A></li>
<LI>Next message: <A HREF="015951.html">[Mageia-dev] Bugzilla mass ping
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#15948">[ date ]</a>
<a href="thread.html#15948">[ thread ]</a>
<a href="subject.html#15948">[ subject ]</a>
<a href="author.html#15948">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>