diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-bugsquad/2012-April/000116.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-bugsquad/2012-April/000116.html')
| -rw-r--r-- | zarb-ml/mageia-bugsquad/2012-April/000116.html | 106 |
1 files changed, 106 insertions, 0 deletions
diff --git a/zarb-ml/mageia-bugsquad/2012-April/000116.html b/zarb-ml/mageia-bugsquad/2012-April/000116.html new file mode 100644 index 000000000..06e64a896 --- /dev/null +++ b/zarb-ml/mageia-bugsquad/2012-April/000116.html @@ -0,0 +1,106 @@ +<!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=%3C201204262214.04511.stormi%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000115.html"> + <LINK REL="Next" HREF="000117.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-bugsquad] Change the version of cauldron bugs ?</H1> + <B>Samuel Verschelde</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=%3C201204262214.04511.stormi%40laposte.net%3E" + TITLE="[Mageia-bugsquad] Change the version of cauldron bugs ?">stormi at laposte.net + </A><BR> + <I>Thu Apr 26 22:14:04 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="000115.html">[Mageia-bugsquad] Change the version of cauldron bugs ? +</A></li> + <LI>Next 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#116">[ date ]</a> + <a href="thread.html#116">[ thread ]</a> + <a href="subject.html#116">[ subject ]</a> + <a href="author.html#116">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le jeudi 26 avril 2012 20:19:15, Manuel Hiebel a écrit : +><i> Hello there, +</I>><i> +</I>><i> I was thinking, what about change the version of "cauldron" bugs to 2 +</I>><i> after the release ? +</I>><i> +</I>><i> Of course we can add some exceptions like: +</I>><i> - the enhancement severity +</I>><i> - the low priority +</I>><i> - the Installer and Release media component +</I>><i> +</I>><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>><i> prio:low+-comp:install+-comp:release +</I>><i> +</I>><i> So this is for now 575 bugs, and I guess it will be less than that we I +</I>><i> plan do to that. +</I>><i> (the list still needs some cleaning) +</I>><i> +</I>><i> Then we can also add a comment, that this is an automatic change and if +</I>><i> it was done wrong, we ask people to revert the change. +</I>><i> +</I>><i> What do you think ? +</I>><i> +</I>><i> (We could also make something like that for the End of life support of +</I>><i> Mageia 1 in 8-9 months) +</I> +Any bug reported against cauldron should be either still valid in Mageia 2 and +therefore fixed by updates, or not valid anymore, so I quite agree. I see +exceptions, for example bugs in the installer or LiveCDs, unless we release +updated ISOs for Mageia 2 in a few months. The main problem is that we lose +information about the bug's validity in cauldron. Last time we discussed it on +this mailing list, IIRC the conclusion was that we needed to be able to set +several releases for the same bug and that a bugzilla update would allow it. +Another option would be duplicate every bug for Mageia 2, and link it to the +cauldron bug (I guess it's quite safe to decide that the Mageia 2 bug must be +blocked by the cauldron bug). It would be my preferred way in fact. + +But I think this must be discussed with other packagers too. + +Also, it would be good to have a report about open bugs in cauldron, per +component or package or group of packages, in a synthetic view, so that we can +have an idea of the quality of the distribution that is to be released (and a +report about Mageia 1 too to see how much bugs we fixed, how much we didn't +fix, what components have the biggest amount of open bugs, still in a +synthetic view... I know, I ask for a lot, and maybe in a few years I will do +it myself :)) + +Best regards + +Samuel Verschelde +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000115.html">[Mageia-bugsquad] Change the version of cauldron bugs ? +</A></li> + <LI>Next 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#116">[ date ]</a> + <a href="thread.html#116">[ thread ]</a> + <a href="subject.html#116">[ subject ]</a> + <a href="author.html#116">[ 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> |