diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101222/001846.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101222/001846.html | 158 |
1 files changed, 158 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101222/001846.html b/zarb-ml/mageia-dev/20101222/001846.html new file mode 100644 index 000000000..54b877f3a --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001846.html @@ -0,0 +1,158 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal for bugzilla + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTikiFvH1H2GTRz%2Byz2NKnfFQJ%3D7AmfcGaQEeOQgq%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001864.html"> + <LINK REL="Next" HREF="001847.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Ahmad Samir</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3CAANLkTikiFvH1H2GTRz%2Byz2NKnfFQJ%3D7AmfcGaQEeOQgq%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">ahmadsamir3891 at gmail.com + </A><BR> + <I>Wed Dec 22 15:27:09 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001864.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001847.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1846">[ date ]</a> + <a href="thread.html#1846">[ thread ]</a> + <a href="subject.html#1846">[ subject ]</a> + <a href="author.html#1846">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 22 December 2010 01:32, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +><i> On Wed, Dec 15, 2010 at 17:07, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I>>><i> +</I>>><i> Le mardi 14 décembre 2010 à 17:05 +0100, Dexter Morgan a écrit : +</I>>><i> > I would like to have your input to let us able to provide a bugzilla really soon +</I>>><i> +</I>>><i> So if I am not wrong, in bugzilla, we have : +</I>>><i> - products +</I>>><i> - component, contained in products +</I>>><i> - and various field, per bug, +</I>>><i> +</I>>><i> and the way we organize everything will impact the layout. +</I>>><i> +</I>><i> +</I>><i> Yes. +</I>><i> +</I>><i> In preparation of the future interaction (by xmlrpc) between the +</I>><i> mageia-app-db site and the mageia bugzilla,  I have been testing +</I>><i> <A HREF="http://bugs.mageia.org/">http://bugs.mageia.org/</A> . +</I>><i> Xmlrpc works, but it will be necessary to configure additional fields. +</I>><i> The minimum would be to add an 'RPM Package' field (such as exists on +</I>><i> <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A>). +</I>><i> +</I> +That's already agreed upon, whatever it's called, RPM Package or +Component (I am in favour of the former). + +><i> But, as the configuration must be modified anyway, I have been +</I>><i> thinking about what fields we need. +</I>><i> +</I>><i> First I think it would be usefull to have a multiline (Large Text Box) +</I>><i> 'RPM Packages' field, instead of a single line (Free Text) field as +</I>><i> used by mandriva. +</I>><i> A single bug can concern more than one rpm. One thing mageia-app-db +</I>><i> will do is search all bugs affecting an rpm. For that search to be +</I>><i> meaningfull all affected rpms should be mentioned. +</I> +'One bug per report' is what we should do (did); if a bug originates +from more than one package, a separate report for each of them should +be opened with the Block/Dependency set correctly. + +><i> For the same reason, the way the rpms are mentioned should be 'standardised', +</I>><i> as the search done by bugzilla can only be litteral. +</I>><i> +</I> +Usually one doesn't only search in the RPM Package field; experience +tell us that the affected package name will be mentioned many times in +both the summary and the description. + +And if you want to search in the RPM Package field, bugzilla has many +options to do so, look at the bottom of: +<A HREF="https://qa.mandriva.com/query.cgi?format=advanced">https://qa.mandriva.com/query.cgi?format=advanced</A> + +><i> Something that does not exist in mandriva, but I think would be usefull, is a +</I>><i> 'Fixed RPM Packages' that would be filled when the bug is fixed. FIXED +</I>><i> is great, but where (or since which rpm)? +</I>><i> +</I> +IMHO, that's trivia; either the user is savvy enough / has the time to +trudge through the bug report to find out which package release fixes +an issue (which indicates he's the curious type, he'll at least skim +through the bug report anyway), or he's just going to update his +system and get the fix (the latter happens more often). + +><i> Perhaps also an 'Upstream' field which would, eventually, indicate +</I>><i> where that bug is filed upstream. +</I>><i> +</I> +That's similar to the URL field in my proposal (see my previous post +in this thread). + +><i> Finally the "status whiteboard" could be enabled, and used to clearly +</I>><i> explain a workaround, for open bugs (instead of having to figure it +</I>><i> from the comments). (Eventually this field could also be used as the +</I>><i> 'Fixed RPM Packages' field when the bug is closed. So it would be the +</I>><i> 'Solution' field) +</I>><i> +</I> +I don't think this will be adequately useful; if the issue is fixed, +then all the user has to do is update his system. If it's not fixed +and affects a stable release then it should get added to the Errata +page for that release whether there's a workaround (or not); if it +affects Cauldron, well, Cauldron users are supposed to be +fireproof-ready, so they do read bug reports (or skim through them). + +><i> Apart from the "status whiteboard" which is a parameter to enable +</I>><i> (<A HREF="http://www.bugzilla.org/docs/tip/en/html/parameters.html">http://www.bugzilla.org/docs/tip/en/html/parameters.html</A>); +</I>><i> the fields must be added as custom-fields +</I>><i> (<A HREF="http://www.bugzilla.org/docs/3.6/en/html/custom-fields.html">http://www.bugzilla.org/docs/3.6/en/html/custom-fields.html</A>) +</I>><i> +</I>><i> +</I>><i> -- +</I>><i> +</I>><i> Frederic +</I>><i> +</I> + + +-- +Ahmad Samir +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001864.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001847.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1846">[ date ]</a> + <a href="thread.html#1846">[ thread ]</a> + <a href="subject.html#1846">[ subject ]</a> + <a href="author.html#1846">[ 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> |