diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006016.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/006016.html | 116 |
1 files changed, 116 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006016.html b/zarb-ml/mageia-dev/2011-June/006016.html new file mode 100644 index 000000000..49b4e3b42 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006016.html @@ -0,0 +1,116 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal of a backporting process + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3CBANLkTikz_TOf-d4bmNdzQYfJ1y5oOhvEdA%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="006015.html"> + <LINK REL="Next" HREF="006017.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal of a backporting process</H1> + <B>Wolfgang Bornath</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3CBANLkTikz_TOf-d4bmNdzQYfJ1y5oOhvEdA%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal of a backporting process">molch.b at googlemail.com + </A><BR> + <I>Sat Jun 25 23:15:30 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006015.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI>Next message: <A HREF="006017.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6016">[ date ]</a> + <a href="thread.html#6016">[ thread ]</a> + <a href="subject.html#6016">[ subject ]</a> + <a href="author.html#6016">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>2011/6/25 Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>>: +><i> On 25 June 2011 22:15, Samuel Verschelde <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stormi at laposte.net</A>> wrote: +</I>>><i> Le samedi 25 juin 2011 21:22:20, Ahmad Samir a écrit : +</I>>>><i> On 25 June 2011 19:33, Samuel Verschelde <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stormi at laposte.net</A>> wrote: +</I>>>><i> > Le vendredi 24 juin 2011 21:39:51, Ahmad Samir a écrit : +</I>>>><i> >> On 24 June 2011 02:09, Michael Scherer <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">misc at zarb.org</A>> wrote: +</I>>>><i> >> > - Someone request a backport ( by bugzilla, by madb, by a email, by +</I>>>><i> >> > taking a packager family in hostage, whatever ). I would prefer use +</I>>>><i> >> > bugzilla but this may not be very user friendly, or too heavy. +</I>>>><i> >> +</I>>>><i> >> How would the packager get notified of backports requests via madb? +</I>>>><i> > +</I>>>><i> > There are several options : +</I>>>><i> > - option 1 : maintainers prefer to have all backports requests in +</I>>>><i> > bugzilla. Madb will then create backports requests via XML-RPC, with the +</I>>>><i> > original reporter in CC maybe, and regularly watch bug report status. +</I>>>><i> > This will be extra work on madb's side and force those users (who maybe +</I>>>><i> > don't know how to use bugzilla) to use 1 tool for the request and a +</I>>>><i> > different tool for testing reports, but why not. +</I>>>><i> > - option 2 : maintainers are OK to use bugzilla for bugs and madb for +</I>>>><i> > package requests => madb will query the maintainers database and notify +</I>>>><i> > the maintainer(s) by mail. It could, like bugzilla, send notifications +</I>>>><i> > to a ML too, and provide a simple yet sufficient tracking system +</I>>>><i> > (status, comments). +</I>>>><i> +</I>>>><i> [...] +</I>>>><i> +</I>>>><i> >> Would you elaborate on how bugzilla is heavy for a backports request? +</I>>>><i> > +</I>>>><i> > Heavy I don't know, but I think that we can give users a better tool to +</I>>>><i> > request backports, see what backports already have been requested, etc. +</I>>>><i> +</I>>>><i> Yes, but what's wrong with bugzilla and better in the other tool? +</I>>><i> +</I>>><i> Bugzilla is an issue tracker, and is centered on that concept. I think that a +</I>>><i> simple "request backport" button in a package database browsing application +</I>>><i> can be easier and more efficient, in that the "need" will be more easily +</I>>><i> transmitted from the user to the packager. The backports requests we get today +</I>>><i> (and got back in mandriva) don't represent the majority of needs. I'd like to +</I>>><i> see what happens if users have a dead simple way to request them. +</I>>><i> +</I>><i> +</I>><i> You want to interface for users, so that they don't have to deal with +</I>><i> a 1minute-to-fill bug report to request a backport... that's your +</I>><i> prerogative, I don' have a problem with that as long as it works. +</I> +The "Request Backport Button" could be a solution for non-english +speakers. They can not use Bugzilla because they can not write in +English to make their request understood, but they can find the +package name in a database and understand the function of a button +which reads "Backport". + +-- +wobo +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006015.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI>Next message: <A HREF="006017.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6016">[ date ]</a> + <a href="thread.html#6016">[ thread ]</a> + <a href="subject.html#6016">[ subject ]</a> + <a href="author.html#6016">[ 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> |