summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/20101223/001879.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/20101223/001879.html')
-rw-r--r--zarb-ml/mageia-dev/20101223/001879.html177
1 files changed, 177 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101223/001879.html b/zarb-ml/mageia-dev/20101223/001879.html
new file mode 100644
index 000000000..79bc07edf
--- /dev/null
+++ b/zarb-ml/mageia-dev/20101223/001879.html
@@ -0,0 +1,177 @@
+<!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=%3C201012232110.19731.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="001873.html">
+ <LINK REL="Next" HREF="001875.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Proposal for bugzilla</H1>
+ <B>Samuel Verschelde</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3C201012232110.19731.stormi%40laposte.net%3E"
+ TITLE="[Mageia-dev] Proposal for bugzilla">stormi at laposte.net
+ </A><BR>
+ <I>Thu Dec 23 21:10:19 CET 2010</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="001873.html">[Mageia-dev] Proposal for bugzilla
+</A></li>
+ <LI>Next message: <A HREF="001875.html">[Mageia-dev] Proposal for bugzilla
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1879">[ date ]</a>
+ <a href="thread.html#1879">[ thread ]</a>
+ <a href="subject.html#1879">[ subject ]</a>
+ <a href="author.html#1879">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le jeudi 23 d&#233;cembre 2010 15:25:10, Ahmad Samir a &#233;crit :
+&gt;<i> On 23 December 2010 00:34, Samuel Verschelde &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stormi at laposte.net</A>&gt; wrote:
+</I>&gt;<i> &gt; Le mercredi 22 d&#233;cembre 2010 21:25:39, Michael scherer a &#233;crit :
+</I>&gt;<i> &gt;&gt; On Wed, Dec 22, 2010 at 01:55:02PM +0100, Frederic Janssens wrote:
+</I>&gt;<i> &gt;&gt; &gt; On 2010-12-22, Michael Scherer &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>&gt; wrote:
+</I>&gt;<i> &gt;&gt; &gt; &gt; Le mercredi 22 d&#233;cembre 2010 &#224; 00:32 +0100, Frederic Janssens a &#233;crit
+</I>:<i>
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; On Wed, Dec 15, 2010 at 17:07, Michael Scherer &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>&gt;
+</I>wrote:
+&gt;<i> &gt;&gt; &gt; &gt;&gt; &gt; Le mardi 14 d&#233;cembre 2010 &#224; 17:05 +0100, Dexter Morgan a &#233;crit :
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; &gt; &gt; I would like to have your input to let us able to provide a
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; &gt; &gt; bugzilla really soon
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; &gt;
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; &gt; So if I am not wrong, in bugzilla, we have :
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; &gt; - products
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; &gt; - component, contained in products
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; &gt; - and various field, per bug,
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; &gt;
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; &gt; and the way we organize everything will impact the layout.
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt;
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; Yes.
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt;
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; In preparation of the future interaction (by xmlrpc) between the
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; mageia-app-db site and the mageia bugzilla, I have been testing
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; <A HREF="http://bugs.mageia.org/">http://bugs.mageia.org/</A> .
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; Xmlrpc works, but it will be necessary to configure additional
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; fields. The minimum would be to add an 'RPM Package' field (such
+</I>&gt;<i> &gt;&gt; &gt; &gt;&gt; as exists on <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A>).
+</I>&gt;<i> &gt;&gt; &gt; &gt;
+</I>&gt;<i> &gt;&gt; &gt; &gt; What about component not related to rpm ?
+</I>&gt;<i> &gt;&gt; &gt;
+</I>&gt;<i> &gt;&gt; &gt; The 'RPM Package' field would be left blank.
+</I>&gt;<i> &gt;&gt; &gt; (usually many fields are left blank)
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; That's quite useless clutter in this case :/
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; &gt; &gt; And do you mean srpm or rpm ?
+</I>&gt;<i> &gt;&gt; &gt;
+</I>&gt;<i> &gt;&gt; &gt; On <A HREF="https://qa.mandriva.com/">https://qa.mandriva.com/</A> anything goes.
+</I>&gt;<i> &gt;&gt; &gt; To permit consistent searches I think we should standardise.
+</I>&gt;<i> &gt;&gt; &gt; The aim would to be to as specific as needed but not more;
+</I>&gt;<i> &gt;&gt; &gt; as far as I know that would be :
+</I>&gt;<i> &gt;&gt; &gt;
+</I>&gt;<i> &gt;&gt; &gt; name-version-release
+</I>&gt;<i> &gt;&gt; &gt;
+</I>&gt;<i> &gt;&gt; &gt; unless the bug is architecture specific, where we would have :
+</I>&gt;<i> &gt;&gt; &gt;
+</I>&gt;<i> &gt;&gt; &gt; name-version-release.architecture
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; There is already a &quot;architecture&quot; field, afaik, as well as a version
+</I>&gt;<i> &gt;&gt; field, no ?
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; ( I didn't check as I refuse to enter my password over a insecured http
+</I>&gt;<i> &gt;&gt; session ).
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; And I think that giving rpm ( and not srpm ) will make search a little
+</I>&gt;<i> &gt;&gt; bit complex in some corner cases ( can will also cause problem for the
+</I>&gt;<i> &gt;&gt; next point ).
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; So you think the (S)RPM field should only contain SRPM filenames ?
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; If yes, I agree with that, because as Frederic stated above, in current
+</I>&gt;<i> &gt; Mandriva bugzilla, there's no enforced rule for that. You can put
+</I>&gt;<i> &gt; anything in the field, and you often end up with rpm filenames, or
+</I>&gt;<i> &gt; simple package names (e.g. &quot;virtualbox&quot;).
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; However asking bug reporters to know the SRPM is too much, so this rule
+</I>&gt;<i> &gt; can only be enforced on Packagers and Triage Team side I think. This is
+</I>&gt;<i> &gt; already how it works on qa.mandriva.com : if you know the SRPM, you put
+</I>&gt;<i> &gt; it, if not someone will triage and do it for you.
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Ahmad, would there be a problem in enforcing such a policy (i.e. SRPM
+</I>&gt;<i> &gt; field should be empty or contain a valid SRPM name ? Where valid means
+</I>&gt;<i> &gt; &quot;looks like the name of a SRPM&quot;) ?
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Regards
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Samuel Verschelde
+</I>&gt;<i>
+</I>&gt;<i> Actually virtualbox is a valid enough SRPM name, because if you put
+</I>&gt;<i> virtualbox in the &quot;RPM Package&quot; field bugzilla will auto-assign to the
+</I>&gt;<i> package maintainer. And putting the arch. of the package in that field
+</I>&gt;<i> isn't so useful, there's a separate Architecture field in each report.
+</I>&gt;<i>
+</I>&gt;<i> How do you wanna enforce this? by rejecting anything the user puts in
+</I>&gt;<i> that field if it's not correct? well, I expect that we'll get less
+</I>&gt;<i> reports this way, good from the triage team workload POV :), bad from
+</I>&gt;<i> the POV that some important reports won't be filed because the user
+</I>&gt;<i> doesn't understand what you want him to do.
+</I>
+By enforcing a policy, I don't mean necessarily rejecting bad or incomplete
+values, but rather ensure that triagers and packagers take care of this field
+and correct it if needed, at least for bugs on stable releases of Mageia.
+
+However misc's remarks about UI-side helpers (autocompletion for example,
+which would propose only the valid package versions for a given package and a
+given distribution version) could help here : if filling the field
+comprehensively becomes easy then it won't be a barrier for unexperienced bug
+reporters and then being stricter becomes possible.
+
+
+&gt;<i>
+</I>&gt;<i> I have no problem with having a report with a wrong content in the RPM
+</I>&gt;<i> Package field, that can be fixed. So no, I am not OK with enforcing
+</I>&gt;<i> anything here, just offering this as a guide line that it should be
+</I>&gt;<i> 'kwrite-4.5.5-1mga' rather than just 'kwrite' or 'kwrite-4.5.5' is the
+</I>&gt;<i> best you can hope for.
+</I>&gt;<i>
+</I>&gt;<i> (IMHO, mageia-app-db should be more versatile in the way it searches
+</I>&gt;<i> bug reports, note that almost at any given point in time there'll be
+</I>&gt;<i> reports that haven't been triaged yet, and so can have an empty or a
+</I>&gt;<i> wrong content in the RPM Package field)
+</I>
+We already plan to be as much versatile as we can be. However like I tried to
+explain in my long off-topic post, we will have to cope with various levels of
+quality of information and treat differently bugs concerning just &quot;kwrite&quot; and
+bugs concerning &quot;kwrite-4.5.5-1mga&quot;.
+
+Regards
+
+Samuel Verschelde
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="001873.html">[Mageia-dev] Proposal for bugzilla
+</A></li>
+ <LI>Next message: <A HREF="001875.html">[Mageia-dev] Proposal for bugzilla
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#1879">[ date ]</a>
+ <a href="thread.html#1879">[ thread ]</a>
+ <a href="subject.html#1879">[ subject ]</a>
+ <a href="author.html#1879">[ 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>