diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006018.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/006018.html | 122 |
1 files changed, 122 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006018.html b/zarb-ml/mageia-dev/2011-June/006018.html new file mode 100644 index 000000000..82607167b --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006018.html @@ -0,0 +1,122 @@ +<!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=%3C1309040220.22020.217.camel%40akroma.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006075.html"> + <LINK REL="Next" HREF="006026.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal of a backporting process</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%20of%20a%20backporting%20process&In-Reply-To=%3C1309040220.22020.217.camel%40akroma.ephaone.org%3E" + TITLE="[Mageia-dev] Proposal of a backporting process">misc at zarb.org + </A><BR> + <I>Sun Jun 26 00:16:59 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006075.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI>Next message: <A HREF="006026.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6018">[ date ]</a> + <a href="thread.html#6018">[ thread ]</a> + <a href="subject.html#6018">[ subject ]</a> + <a href="author.html#6018">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le vendredi 24 juin 2011 à 22:39 +0300, Ahmad Samir a écrit : +><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> > Hi, +</I>><i> > +</I>><i> > as said in the thread of firefox 5, and in the meeting of packager +</I>><i> > sooner this week, this is the first mail about backports ( on 3 ). +</I>><i> > +</I>><i> > So here is the proposal of a process, based on the feedback of people, +</I>><i> > and the idea of some packagers ( mainly stormi ). +</I>><i> > +</I>><i> > +</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> +</I>><i> Would you elaborate on how bugzilla is heavy for a backports request? +</I> +It requires a more formal process, requires to fill a proper bug ( thus +either requesting more experience, or more work from triaging ). + +While bugzilla would work, I think we could have a more streamlined and +direct way of requesting backport. Maybe a custom template in bugzilla +would do the trick. + +><i> > - based on feedback ( ie if the package work or if the packager is +</I>><i> > confident ), the packager decide to move it to backport for everybody, +</I>><i> > using some stuff similar to rpmctl ( the tool we used to move package at +</I>><i> > Mandriva ). The tool would also send notifications. +</I>><i> > +</I>><i> +</I>><i> The packager decides to move it and he has the necessary privileges to +</I>><i> do so? or will he have to request someone from another team to move +</I>><i> it? +</I> +The packager decide to move. + +><i> > This way : +</I>><i> > - packages are not sent untested, thus raising confidence in backports +</I>><i> +</I>><i> How many times did backports breaks a user's whole installation? +</I> +Not often. But the issue is not if the system is broken beyond repair, +as it didn't happen, and would surely not happen with the proposed +policy. But even if system work, people will perceive backport has being +unreliable if some of them do not work. + + +><i> we +</I>><i> always say that backports should mainly be cherry picked, but not +</I>><i> enabled all the time... so how does installing a new version of e.g. +</I>><i> wine break the user's system when he can easily back out that rpm? +</I> +I a not sure that most people realize they can revert. Maybe a easier +interface to do that could be offered ( along maybe with a tool that +send feedback on why it did downgrade it ? ). +-- +Michael Scherer + +</PRE> + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006075.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI>Next message: <A HREF="006026.html">[Mageia-dev] Proposal of a backporting process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6018">[ date ]</a> + <a href="thread.html#6018">[ thread ]</a> + <a href="subject.html#6018">[ subject ]</a> + <a href="author.html#6018">[ 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> |