diff options
Diffstat (limited to 'zarb-ml/mageia-bugsquad/2012-April/000118.html')
| -rw-r--r-- | zarb-ml/mageia-bugsquad/2012-April/000118.html | 149 |
1 files changed, 149 insertions, 0 deletions
diff --git a/zarb-ml/mageia-bugsquad/2012-April/000118.html b/zarb-ml/mageia-bugsquad/2012-April/000118.html new file mode 100644 index 000000000..b95351997 --- /dev/null +++ b/zarb-ml/mageia-bugsquad/2012-April/000118.html @@ -0,0 +1,149 @@ +<!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=%3C4F9E9A97.9070607%40hiebel.eu%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000117.html"> + + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-bugsquad] Change the version of cauldron bugs ?</H1> + <B>Manuel Hiebel</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=%3C4F9E9A97.9070607%40hiebel.eu%3E" + TITLE="[Mageia-bugsquad] Change the version of cauldron bugs ?">manuel at hiebel.eu + </A><BR> + <I>Mon Apr 30 15:58:47 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="000117.html">[Mageia-bugsquad] Change the version of cauldron bugs ? +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#118">[ date ]</a> + <a href="thread.html#118">[ thread ]</a> + <a href="subject.html#118">[ subject ]</a> + <a href="author.html#118">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Thanks for your replay + +Le 28/04/2012 12:16, Marja van Waes a écrit : +><i> On 26/04/12 22:14, Samuel Verschelde wrote: +</I>>><i> Le jeudi 26 avril 2012 20:19:15, Manuel Hiebel a écrit : +</I>>>><i> [...] +</I>>><i> Any bug reported against cauldron should be either still valid in +</I>>><i> Mageia 2 and +</I>>><i> therefore fixed by updates, or not valid anymore, so I quite agree. I +</I>>><i> see +</I>>><i> exceptions, for example bugs in the installer or LiveCDs, unless we +</I>>><i> release +</I>>><i> updated ISOs for Mageia 2 in a few months. +</I>That's why I have added some exceptions in my bug list. + +>><i> The main problem is that we lose +</I>>><i> information about the bug's validity in cauldron. +</I>Indeed +><i> Another main problem is we don't know whether they're still valid or +</I>><i> not. We don't ask reporters every month whether the issue is still +</I>><i> there. We ping bugs after 3 months, if nothing happened to the report, +</I>><i> but if I don't have time to check whether there is a possibility the +</I>><i> bug got fixed, I usually don't ask whether it is still valid. +</I> +We could ask at the same time of the change. +I guess in the future this method will be hard to keep no ? (ping after +3 months of inactivity) +That's why, I proposed to close only at the End of Life of the release +all bugs of the unsupported version, and ask people to upgrade and +reopen if still valid (fedora do that iirc). + +><i> For me it would be confusing if all cauldron bugs were set to be +</I>><i> Mageia 2 stable bugs (too), because when I see that I expect that at +</I>><i> least one person reported the bug was valid for mageia 2 stable. +</I>Indeed, if people don't close bugs after our request it can make false +positive. +><i> +</I>><i> Of course, for bugs that were filed recently, that will often be the +</I>><i> case, but many cauldron bugs were not filed that recently, some date +</I>><i> from before mageia 1 release, many from 2 alpha. +</I>><i> +</I>><i> +</I>>><i> Last time we discussed it on +</I>>><i> this mailing list, IIRC the conclusion was that we needed to be able +</I>>><i> to set +</I>>><i> several releases for the same bug and that a bugzilla update would +</I>>><i> allow it. +</I>>><i> Another option would be duplicate every bug for Mageia 2, and link it +</I>>><i> to the +</I>>><i> cauldron bug (I guess it's quite safe to decide that the Mageia 2 bug +</I>>><i> must be +</I>>><i> blocked by the cauldron bug). It would be my preferred way in fact. +</I>I have searched on this ml or on -dev an found nothing. :/ +What was the topic ? + +For the duplicate bugs, why not but it seems hard to manage. +><i> +</I>><i> I agree, if their validity is checked first. +</I>><i> +</I>><i> I'd like to see that the moment 2 stable is released, all cauldron +</I>><i> bugs are pinged and all reporters/commenters are asked to clone the +</I>><i> bug for Mageia 2 if it is valid for stable, and set it to depend on +</I>><i> the original bug. If it isn't valid for stable, it most probably can't +</I>><i> be valid for cauldron anymore, so it would be safe to close them as old. +</I>><i> +</I>><i> I think we'll end up closing a lot of cauldron bugs :) +</I>>><i> +</I>>><i> But I think this must be discussed with other packagers too. +</I>Yep, but better have something where the bugsquad is agree. :) +>><i> +</I>>><i> Also, it would be good to have a report about open bugs in cauldron, per +</I>>><i> component or package or group of packages, in a synthetic view, so +</I>>><i> that we can +</I>>><i> have an idea of the quality of the distribution that is to be +</I>>><i> released (and a +</I>>><i> report about Mageia 1 too to see how much bugs we fixed, how much we +</I>>><i> didn't +</I>>><i> fix, what components have the biggest amount of open bugs, still in a +</I>>><i> synthetic view... I know, I ask for a lot, and maybe in a few years I +</I>>><i> will do +</I>>><i> it myself :)) +</I>><i> +</I>><i> +</I>><i> Can you point me to an example of a report in a synthetic view? +</I>Something like that ? + +<A HREF="https://bugs.mageia.org/report.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_id_type=anyexact&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&chfieldfrom=&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailqa_contact2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&longdesc=&longdesc_type=allwordssubstr&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&x_axis_field=bug_status&x_labels_vertical=1&z_axis_field=component&width=600&height=350&action=wrap&format=bar">https://bugs.mageia.org/report.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_id_type=anyexact&bug_status=NEW&bug_status=UNCONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&chfieldfrom=&chfieldto=Now&chfieldvalue=&email1=&email2=&emailassigned_to1=1&emailassigned_to2=1&emailcc2=1&emailqa_contact2=1&emailreporter2=1&emailtype1=substring&emailtype2=substring&field0-0-0=noop&keywords=&keywords_type=allwords&longdesc=&longdesc_type=allwordssubstr&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type0-0-0=noop&value0-0-0=&x_axis_field=bug_status&x_labels_vertical=1&z_axis_field=component&width=600&height=350&action=wrap&format=bar</A> + +Graphiz was installed on the bugzilla, but not the function to make +report against the time. +><i> +</I>><i> +</I>>><i> +</I>>><i> Best regards +</I>>><i> +</I>>><i> Samuel Verschelde +</I></PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000117.html">[Mageia-bugsquad] Change the version of cauldron bugs ? +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#118">[ date ]</a> + <a href="thread.html#118">[ thread ]</a> + <a href="subject.html#118">[ subject ]</a> + <a href="author.html#118">[ 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> |