diff options
Diffstat (limited to 'zarb-ml/mageia-bugsquad/2011-October/000054.html')
| -rw-r--r-- | zarb-ml/mageia-bugsquad/2011-October/000054.html | 162 |
1 files changed, 162 insertions, 0 deletions
diff --git a/zarb-ml/mageia-bugsquad/2011-October/000054.html b/zarb-ml/mageia-bugsquad/2011-October/000054.html new file mode 100644 index 000000000..380f26dd0 --- /dev/null +++ b/zarb-ml/mageia-bugsquad/2011-October/000054.html @@ -0,0 +1,162 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-bugsquad] Wiki struscture + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-bugsquad%40mageia.org?Subject=Re%3A%20%5BMageia-bugsquad%5D%20Wiki%20struscture&In-Reply-To=%3C4E8A2860.1010808%40xs4all.nl%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000053.html"> + <LINK REL="Next" HREF="000055.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-bugsquad] Wiki struscture</H1> + <B>Marja van Waes</B> + <A HREF="mailto:mageia-bugsquad%40mageia.org?Subject=Re%3A%20%5BMageia-bugsquad%5D%20Wiki%20struscture&In-Reply-To=%3C4E8A2860.1010808%40xs4all.nl%3E" + TITLE="[Mageia-bugsquad] Wiki struscture">marja11 at xs4all.nl + </A><BR> + <I>Mon Oct 3 23:25:52 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="000053.html">[Mageia-bugsquad] Wiki struscture +</A></li> + <LI>Next message: <A HREF="000055.html">[Mageia-bugsquad] assigned long ago but still new +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#54">[ date ]</a> + <a href="thread.html#54">[ thread ]</a> + <a href="subject.html#54">[ subject ]</a> + <a href="author.html#54">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op 03-10-11 16:45, Samuel Verschelde schreef: +><i> +</I>><i> Le dimanche 2 octobre +</I>><i> 2011 22:38:45, vous avez écrit : +</I>><i> +</I>><i> > Op 02-10-11 22:28, +</I>><i> Samuel Verschelde schreef: +</I>><i> +</I>><i> +</I>><i> > > +</I>><i> +</I>><i> > > A bug reported +</I>><i> against cauldron and still valid becomes a bug reported +</I>><i> +</I>><i> > > against Mageia +</I>><i> 2. If we don't change the Version field from cauldron to +</I>><i> +</I>><i> > > Mageia 2, we +</I>><i> risk having some bugs fixed only in cauldron without an +</I>><i> +</I>><i> > > update being +</I>><i> issued in Mageia 2. +</I>><i> +</I>><i> > +</I>><i> +</I>><i> > And copying it, so +</I>><i> that there is the same report against cauldron as +</I>><i> +</I>><i> > against Mageia 2? +</I>><i> +</I>><i> +</I>><i> +</I>><i> Maybe. It could be a lot +</I>><i> of work to maintain 2 versions of the same bug report. +</I>><i> +</I>><i> +</I> +If you keep it in one report and the Cauldron bug gets solved by an +update, how is one going to see at first sight that it wasn't resolved +for the official release. What status should it get? It can't be +"resolved fixed" if it still exists in another release. + + +><i> +</I>><i> > Bugs on different +</I>><i> releases should go into seperate Bug +</I>><i> +</I>><i> > reports, according +</I>><i> to our manual. The Mageia 2 one is then set to depend +</I>><i> +</I>><i> > on the cauldron +</I>><i> one, and the cauldron one is set to block the mageia 2 +</I>><i> +</I>><i> > one (because a +</I>><i> patch is, of course, going to be tested in Cauldron first) +</I>><i> +</I>><i> +</I>><i> +</I>><i> I'm not sure. A bug +</I>><i> could have been fixed in cauldron by updating to a newer version +</I>><i> (independently of the bug report), but still remain in Mageia 2. +</I>><i> And I've seen many bugs fixed in Mageia 1 before or at the same +</I>><i> time as in cauldron. +</I>><i> +</I>><i> +</I>><i> +</I>><i> It's not an easy +</I>><i> subject, the solution must be thinked of, taking every case into +</I>><i> account. +</I>><i> +</I>><i> +</I>Those bugs fixed in Mageia 1 before cauldron, were they set to "depends +on $cauldron bug number"? + +Ideally, if the cauldron bug gets fixed by an update, it stops blocking +the Mageia 1 bug, so the maintainer can then concentrate on solving the +Mageia 1 bug. And if the blocker was properly set, he'll know the bug is +still in Mageia 1 + +Whatever solution is chosen, it should be made very clear in the Triage +guide. At the moment this part states: + + + +**************************************************************** + +What if the same bug affects two different releases? + +Identical bugs filed on different releases should not be closed as +duplicates. +For instance, if a bug is reported on Cauldron and then subsequently on +a stable release, do not close the second report as a duplicate of the +first. +The reason for this is that resolution of a bug in one distribution does +not imply resolution of the same bug in another distribution, so under +the current Bugzilla system, having separate reports for each +distribution is the best way to handle such situations. +You have to also set blockers and depends properly: cauldron bug blocks +other mageia versions bugs. + +********************************************************************************* + + + +Regards, +Marja +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000053.html">[Mageia-bugsquad] Wiki struscture +</A></li> + <LI>Next message: <A HREF="000055.html">[Mageia-bugsquad] assigned long ago but still new +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#54">[ date ]</a> + <a href="thread.html#54">[ thread ]</a> + <a href="subject.html#54">[ subject ]</a> + <a href="author.html#54">[ 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> |