summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-bugsquad/2012-April/000117.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-bugsquad/2012-April/000117.html')
-rw-r--r--zarb-ml/mageia-bugsquad/2012-April/000117.html145
1 files changed, 145 insertions, 0 deletions
diff --git a/zarb-ml/mageia-bugsquad/2012-April/000117.html b/zarb-ml/mageia-bugsquad/2012-April/000117.html
new file mode 100644
index 000000000..aef892e1e
--- /dev/null
+++ b/zarb-ml/mageia-bugsquad/2012-April/000117.html
@@ -0,0 +1,145 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-bugsquad] Change the version of cauldron bugs ?
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-bugsquad%40mageia.org?Subject=Re%3A%20%5BMageia-bugsquad%5D%20Change%20the%20version%20of%20cauldron%20bugs%20%3F&In-Reply-To=%3C4F9BC370.4010806%40xs4all.nl%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000116.html">
+ <LINK REL="Next" HREF="000118.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-bugsquad] Change the version of cauldron bugs ?</H1>
+ <B>Marja van Waes</B>
+ <A HREF="mailto:mageia-bugsquad%40mageia.org?Subject=Re%3A%20%5BMageia-bugsquad%5D%20Change%20the%20version%20of%20cauldron%20bugs%20%3F&In-Reply-To=%3C4F9BC370.4010806%40xs4all.nl%3E"
+ TITLE="[Mageia-bugsquad] Change the version of cauldron bugs ?">marja11 at xs4all.nl
+ </A><BR>
+ <I>Sat Apr 28 12:16:16 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000116.html">[Mageia-bugsquad] Change the version of cauldron bugs ?
+</A></li>
+ <LI>Next message: <A HREF="000118.html">[Mageia-bugsquad] Change the version of cauldron bugs ?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#117">[ date ]</a>
+ <a href="thread.html#117">[ thread ]</a>
+ <a href="subject.html#117">[ subject ]</a>
+ <a href="author.html#117">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>On 26/04/12 22:14, Samuel Verschelde wrote:
+&gt;<i> Le jeudi 26 avril 2012 20:19:15, Manuel Hiebel a &#233;crit :
+</I>&gt;&gt;<i> Hello there,
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> I was thinking, what about change the version of &quot;cauldron&quot; bugs to 2
+</I>&gt;&gt;<i> after the release ?
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Of course we can add some exceptions like:
+</I>&gt;&gt;<i> - the enhancement severity
+</I>&gt;&gt;<i> - the low priority
+</I>&gt;&gt;<i> - the Installer and Release media component
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> <A HREF="https://bugs.mageia.org/buglist.cgi?quicksearch=version:cauldron+-sev:enh+-">https://bugs.mageia.org/buglist.cgi?quicksearch=version:cauldron+-sev:enh+-</A>
+</I>&gt;&gt;<i> prio:low+-comp:install+-comp:release
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> So this is for now 575 bugs, and I guess it will be less than that we I
+</I>&gt;&gt;<i> plan do to that.
+</I>&gt;&gt;<i> (the list still needs some cleaning)
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Then we can also add a comment, that this is an automatic change and if
+</I>&gt;&gt;<i> it was done wrong, we ask people to revert the change.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> What do you think ?
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> (We could also make something like that for the End of life support of
+</I>&gt;&gt;<i> Mageia 1 in 8-9 months)
+</I>&gt;<i>
+</I>&gt;<i> Any bug reported against cauldron should be either still valid in Mageia 2 and
+</I>&gt;<i> therefore fixed by updates, or not valid anymore, so I quite agree. I see
+</I>&gt;<i> exceptions, for example bugs in the installer or LiveCDs, unless we release
+</I>&gt;<i> updated ISOs for Mageia 2 in a few months. The main problem is that we lose
+</I>&gt;<i> information about the bug's validity in cauldron.
+</I>
+Another main problem is we don't know whether they're still valid or
+not. We don't ask reporters every month whether the issue is still
+there. We ping bugs after 3 months, if nothing happened to the report,
+but if I don't have time to check whether there is a possibility the bug
+got fixed, I usually don't ask whether it is still valid.
+
+For me it would be confusing if all cauldron bugs were set to be Mageia
+2 stable bugs (too), because when I see that I expect that at least one
+person reported the bug was valid for mageia 2 stable.
+
+Of course, for bugs that were filed recently, that will often be the
+case, but many cauldron bugs were not filed that recently, some date
+from before mageia 1 release, many from 2 alpha.
+
+
+&gt;<i> Last time we discussed it on
+</I>&gt;<i> this mailing list, IIRC the conclusion was that we needed to be able to set
+</I>&gt;<i> several releases for the same bug and that a bugzilla update would allow it.
+</I>&gt;<i> Another option would be duplicate every bug for Mageia 2, and link it to the
+</I>&gt;<i> cauldron bug (I guess it's quite safe to decide that the Mageia 2 bug must be
+</I>&gt;<i> blocked by the cauldron bug). It would be my preferred way in fact.
+</I>
+
+I agree, if their validity is checked first.
+
+I'd like to see that the moment 2 stable is released, all cauldron bugs
+are pinged and all reporters/commenters are asked to clone the bug for
+Mageia 2 if it is valid for stable, and set it to depend on the original
+bug. If it isn't valid for stable, it most probably can't be valid for
+cauldron anymore, so it would be safe to close them as old.
+
+I think we'll end up closing a lot of cauldron bugs :)
+&gt;<i>
+</I>&gt;<i> But I think this must be discussed with other packagers too.
+</I>&gt;<i>
+</I>&gt;<i> Also, it would be good to have a report about open bugs in cauldron, per
+</I>&gt;<i> component or package or group of packages, in a synthetic view, so that we can
+</I>&gt;<i> have an idea of the quality of the distribution that is to be released (and a
+</I>&gt;<i> report about Mageia 1 too to see how much bugs we fixed, how much we didn't
+</I>&gt;<i> fix, what components have the biggest amount of open bugs, still in a
+</I>&gt;<i> synthetic view... I know, I ask for a lot, and maybe in a few years I will do
+</I>&gt;<i> it myself :))
+</I>
+
+Can you point me to an example of a report in a synthetic view?
+
+
+&gt;<i>
+</I>&gt;<i> Best regards
+</I>&gt;<i>
+</I>&gt;<i> Samuel Verschelde
+</I>&gt;<i> _______________________________________________
+</I>&gt;<i> Mageia-bugsquad mailing list
+</I>&gt;<i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-bugsquad">Mageia-bugsquad at mageia.org</A>
+</I>&gt;<i> <A HREF="https://www.mageia.org/mailman/listinfo/mageia-bugsquad">https://www.mageia.org/mailman/listinfo/mageia-bugsquad</A>
+</I>
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000116.html">[Mageia-bugsquad] Change the version of cauldron bugs ?
+</A></li>
+ <LI>Next message: <A HREF="000118.html">[Mageia-bugsquad] Change the version of cauldron bugs ?
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#117">[ date ]</a>
+ <a href="thread.html#117">[ thread ]</a>
+ <a href="subject.html#117">[ subject ]</a>
+ <a href="author.html#117">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-bugsquad">More information about the Mageia-bugsquad
+mailing list</a><br>
+</body></html>