diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101222/001851.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101222/001851.html | 187 |
1 files changed, 187 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101222/001851.html b/zarb-ml/mageia-dev/20101222/001851.html new file mode 100644 index 000000000..acd9231b7 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001851.html @@ -0,0 +1,187 @@ +<!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=%3CAANLkTikPaTi%3DN-Fy-eUeuQPEJC9Ep-ZDBOcKvgPP74F7%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="001849.html"> + <LINK REL="Next" HREF="001858.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=%3CAANLkTikPaTi%3DN-Fy-eUeuQPEJC9Ep-ZDBOcKvgPP74F7%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">ahmadsamir3891 at gmail.com + </A><BR> + <I>Wed Dec 22 20:34:18 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001849.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001858.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1851">[ date ]</a> + <a href="thread.html#1851">[ thread ]</a> + <a href="subject.html#1851">[ subject ]</a> + <a href="author.html#1851">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 22 December 2010 21:25, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +><i> On 2010-12-22, Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> wrote: +</I>>><i> On 22 December 2010 18:37, Frederic Janssens <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">fjanss at gmail.com</A>> wrote: +</I>>>><i> On 2010-12-22, Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> wrote: +</I>>>>><i> 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>><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>>>>><i> +</I>>>>><i> 'One bug per report' is what we should do (did); if a bug originates +</I>>>>><i> from more than one package, a separate report for each of them should +</I>>>>><i> be opened with the Block/Dependency set correctly. +</I>>>><i> +</I>>>><i> Sorry for not beeing clear. +</I>>>><i> What I propose is not for the case 'a bug originates from more than +</I>>>><i> one package'; +</I>>>><i> but for the case 'a bug manifests itself in than one package'. +</I>>><i> +</I>>><i> A bug that manifests in more than one package must originate from +</I>>><i> 'some package', that 'some package' is the only one that should be in +</I>>><i> the 'RPM Package' field; i.e that's the package that's going to need +</I>>><i> fixing. +</I>><i> +</I>><i> Sorry again, what I mean, and should have written, is : +</I>><i> 'a bug manifests itself in one package, but in more than one -version-release'. +</I>><i> +</I> +There's no way in bugzilla to do this at the moment (there's talk +about this being implemented in bugzilla-4.0, which I haven't tried +before). Traditionally the Whiteboard field was used for such issues +(or separate reports were opened for each affected stable release). +Having a multi-line RPM Package wouldn't be the way to go with this +(IMHO). + +>>><i> (In fact I think I want to solve the same problem you want to solve with +</I>>>><i> "with a whiteboard field to state if the bug affects more than one release +</I>>>><i> (at +</I>>>><i> least for now)" +</I>>>><i> but in a more specific manner). +</I>><i> +</I>><i> +</I>><i> +</I>>>><i> +</I>>>>><i> +</I>>>>>><i> For the same reason, the way the rpms are mentioned should be +</I>>>>>><i> 'standardised', +</I>>>>>><i> as the search done by bugzilla can only be litteral. +</I>>>>>><i> +</I>>>>><i> +</I>>>>><i> Usually one doesn't only search in the RPM Package field; experience +</I>>>>><i> tell us that the affected package name will be mentioned many times in +</I>>>>><i> both the summary and the description. +</I>>>>><i> +</I>>>>><i> And if you want to search in the RPM Package field, bugzilla has many +</I>>>>><i> options to do so, look at the bottom of: +</I>>>>><i> <A HREF="https://qa.mandriva.com/query.cgi?format=advanced">https://qa.mandriva.com/query.cgi?format=advanced</A> +</I>>>><i> +</I>>>><i> Yes; but I am trying to solve the connection with mageia-app-db. +</I>>>><i> With the xmlrpc interface it seems the search possibilities are more +</I>>>><i> limited : +</I>>>><i> (from +</I>>>><i> <A HREF="http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/WebService/Bug.html">http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/WebService/Bug.html</A>) +</I>>>><i> : +</I>>>><i> +</I>>>><i> " +</I>>>><i> search +</I>>>><i> +</I>>>><i>    UNSTABLE +</I>>>><i> +</I>>>><i>    Description +</I>>>><i> +</I>>>><i>        Allows you to search for bugs based on particular criteria. +</I>>>><i>    Params +</I>>>><i> +</I>>>><i>        Unless otherwise specified in the description of a parameter, +</I>>>><i> bugs are returned if they match exactly the criteria you specify in +</I>>>><i> these parameters. That is, we don't match against substrings--if a bug +</I>>>><i> is in the "Widgets" product and you ask for bugs in the "Widg" +</I>>>><i> product, you won't get anything. +</I>>>><i> +</I>>>><i>        Criteria are joined in a logical AND. That is, you will be +</I>>>><i> returned bugs that match all of the criteria, not bugs that match any +</I>>>><i> of the criteria. +</I>>>><i> +</I>>>><i>        Each parameter can be either the type it says, or an array of +</I>>>><i> the types it says. If you pass an array, it means "Give me bugs with +</I>>>><i> any of these values." For example, if you wanted bugs that were in +</I>>>><i> either the "Foo" or "Bar" products, you'd pass: +</I>>>><i> +</I>>>><i>         product => ['Foo', 'Bar'] +</I>>>><i> " +</I>>>><i> +</I>>><i> +</I>>><i> I don't know about xmlrpc, but there's no one certain way to fill the +</I>>><i> 'RPM Package' field; ideally it should be packagename-version-release +</I>>><i> (e.g. kwrite-4.5.85-1mdv), +</I>><i> +</I>><i> That's what I proposed in another post. +</I>><i> If that were the standard, there would be no problem for mageia-app-db. +</I>><i> +</I>>><i> whatever search method you use, it has to +</I>>><i> be versatile enough to cope with the field content variations. +</I>><i> +</I>><i> To be clear : as indicated above, +</I>><i> the limitation is in what bugzilla offers through it's xmlrpc interface. +</I>><i> We should have to modify the bugzilla code if we wanted access to it's +</I>><i> 'advanced search' +</I>><i> through it's xmlrpc interface. +</I>><i> +</I> +Whatever. As long as that doesn't affect the workflow of the triage +team or bugzilla's performance in general, I don't really care +whichever way it get implemented :) + +[...] + +><i> -- +</I>><i> +</I>><i> Frederic +</I>><i> +</I> + + +-- +Ahmad Samir +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001849.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI>Next message: <A HREF="001858.html">[Mageia-dev] Proposal for bugzilla +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1851">[ date ]</a> + <a href="thread.html#1851">[ thread ]</a> + <a href="subject.html#1851">[ subject ]</a> + <a href="author.html#1851">[ 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> |