diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101222/001861.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101222/001861.html | 124 |
1 files changed, 124 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101222/001861.html b/zarb-ml/mageia-dev/20101222/001861.html new file mode 100644 index 000000000..a9ffb23f7 --- /dev/null +++ b/zarb-ml/mageia-dev/20101222/001861.html @@ -0,0 +1,124 @@ +<!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=%3C201012222323.26718.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001859.html"> + + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal for bugzilla</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20for%20bugzilla&In-Reply-To=%3C201012222323.26718.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Proposal for bugzilla">maarten.vanraes at gmail.com + </A><BR> + <I>Wed Dec 22 23:23:26 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001859.html">[Mageia-dev] Proposal for bugzilla +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1861">[ date ]</a> + <a href="thread.html#1861">[ thread ]</a> + <a href="subject.html#1861">[ subject ]</a> + <a href="author.html#1861">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op woensdag 22 december 2010 22:30:00 schreef andre999: +><i> Dexter Morgan a écrit : +</I>><i> > hello, +</I>><i> > +</I>><i> > now that we have a working bugzilla we need to have a working layout. +</I>><i> > +</I>><i> > i created a wiki page presenting what could be done. +</I>><i> > <A HREF="http://mageia.org/wiki/doku.php?id=bugzilla">http://mageia.org/wiki/doku.php?id=bugzilla</A> +</I>><i> > +</I>><i> > I would like to have your input to let us able to provide a bugzilla +</I>><i> > really soon +</I>><i> > +</I>><i> > +</I>><i> > In the bugreport creation we were thinking of using the mdv way or the +</I>><i> > fedora way. +</I>><i> > +</I>><i> > +</I>><i> > Fedora way is to add all srpms in the componment field but there is 2 +</I>><i> > pbs with this way : +</I>><i> > +</I>><i> > -> Users don't know what is a rpms ( like what is the srpms for kwrite ) +</I>><i> > -> This slow down the bugzilla too much +</I>><i> +</I>><i> Reaction from an end-user that has filed/commented/viewed a lot of bug +</I>><i> reports. +</I>><i> +</I>><i> - I like the idea of separating +</I>><i> -- main bug reports. +</I>><i> All releases together. A lot of end-users are not very aware of the +</I>><i> version/release of the software with the bug until they are well into +</I>><i> the reporting process. So selecting the release would be better delayed +</I>><i> to the bug report entry page. +</I>><i> Plus the idea of eventually having bugs applying to multiple releases +</I>><i> (mentioned on another post) sounds good, as well. +</I>><i> +</I>><i> -- documentation +</I>><i> Tends to be reported/corrected by different people than software bugs. +</I> +good call + +><i> -- localisation (maybe combined with documentation ?) +</I>><i> Also tends to be reported by different people than software bugs, and +</I>><i> corrected by translators. +</I> +again good call + +><i> -- cauldron +</I> +i doubt this + +><i> - Better to avoid listing .srpm's. Most end-users filing bug reports +</I>><i> have no idea what they are. So no point in slowing down bugzilla for that. +</I>><i> And from the .rpm, packagers/developers will be able to find the .srpm +</I>><i> quickly enough. +</I> +actually, the triage team finds this alot quicker than package maintainers, +they often only care about their own package, and if it's not assigned to +their package they won't be looking for it. + +i do agree that users often have no clue of what specific component is +responsible for what, and they often get it wrong if they try. + +><i> - The idea of a multiline .rpm field (mentioned on another post) seems +</I>><i> an excellent idea. Better to list all related .rpm's in one location +</I>><i> than putting additional .rpms into the description and/or comment +</I>><i> fields. (Not only for mageia-app-db.) +</I>><i> +</I>><i> my 2 cents :) +</I></PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001859.html">[Mageia-dev] Proposal for bugzilla +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1861">[ date ]</a> + <a href="thread.html#1861">[ thread ]</a> + <a href="subject.html#1861">[ subject ]</a> + <a href="author.html#1861">[ 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> |