diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005971.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005971.html | 134 |
1 files changed, 134 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005971.html b/zarb-ml/mageia-dev/2011-June/005971.html new file mode 100644 index 000000000..aaf90954b --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005971.html @@ -0,0 +1,134 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Firefox 5 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Firefox%205&In-Reply-To=%3CBANLkTim8AqA5Vwk-SBHcpyxJjHubsNgYWQ%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="005972.html"> + <LINK REL="Next" HREF="005973.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Firefox 5</H1> + <B>Ahmad Samir</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Firefox%205&In-Reply-To=%3CBANLkTim8AqA5Vwk-SBHcpyxJjHubsNgYWQ%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Firefox 5">ahmadsamir3891 at gmail.com + </A><BR> + <I>Fri Jun 24 00:17:57 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005972.html">[Mageia-dev] Firefox 5 +</A></li> + <LI>Next message: <A HREF="005973.html">[Mageia-dev] Firefox 5 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5971">[ date ]</a> + <a href="thread.html#5971">[ thread ]</a> + <a href="subject.html#5971">[ subject ]</a> + <a href="author.html#5971">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 23 June 2011 23:48, David W. Hodgins <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">davidwhodgins at gmail.com</A>> wrote: +><i> On Thu, 23 Jun 2011 15:52:30 -0400, Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> +</I>><i> wrote: +</I>><i> +</I>>><i> On 23 June 2011 07:58, Dexter Morgan <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dmorganec at gmail.com</A>> wrote: +</I>><i> +</I>>>><i> yes it needs to go to backports_testing before iirc +</I>><i> +</I>>><i> Got a link to a thread on -dev ML / irc meeting log / <insert your +</I>>><i> favourite communication method here>, where this was decided? +</I>><i> +</I>><i> This mailing list, thread "Release cycles proposals, and discussion", +</I>><i> messageid BANLkTimrPR-=<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">UgQOnfvAkqPft80LNi9seQ at mail.gmail.com</A> +</I>><i> +</I>><i> Where Anne posted ... +</I>><i> +</I>>><i> exactly what I had in mind. Having backports can allow choice between +</I>>><i> "the last version of" and "the stable version with which I'm happy +</I>>><i> with". But indeed we need more quality in backport rpms that is policy +</I>>><i> and tests. +</I>><i> +</I>><i> In order for the qa team to perform the tests, before they go to the +</I>><i> backports repository, they have to go to to the testing repository +</I>><i> first. +</I>><i> +</I> +1) It doesn't say "we're going to use backports_testing", does it? +guessing != an instated policy +2) IMHO, QA is too small to handle backports too + +><i> Something that works in cauldron may not work when moved to backports, +</I>><i> if a dependency is missed.  By using backports_testing, we can catch +</I>><i> that before it hits the average user. +</I>><i> +</I>><i> Regards, Dave Hodgins +</I>><i> +</I> +Right so, the plan is: +- A packager submits to backports_testing and assigns to QA +- QA tests, the package is good to go +- The report is assigned to <whoever has privileges to move packages +from backports_testing to backports>, atm that's sysadm team +- Package is moved and the report closed + +Caveats: +- QA is too small, and it'll take time/effort to get through the +backported packages requiring tests, unless you depend on the user +asking for the backport to have tested the package properly, the user +will say it works if it works on his box for the arch he's using, he +won't do both archs, not just because he's lazy, but maybe he has one +Mageia box for example +- Sysadm team is already overworked with many other tasks, meaning the +packages requiring a move will rot for a while in backports_testing. + +Now compare that to what's used in e.g. mdv: +- User asks for a backport +- Packager submits the backport and closes the report + +Do you see the problem I am talking about yet? adding more complexity +to backporting may result in less backports; the more the hoops, the +less the backports, the more the users' complaints about +I-want-the-latest-version-of-foo-yesterday. + +The "quality of backports" is a sentence that lacks statistics and +numbers; in e.g. mdv, how many packages were backported to release +foo? how many of them worked(tm)? how many of them didn't work and +required a bit of fixing? how many of them didn't work and won't work +due to any number of reasons? + +I think backports in mdv worked pretty well all those years, not all +of them worked, but most of them did. + +-- +Ahmad Samir +</PRE> + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005972.html">[Mageia-dev] Firefox 5 +</A></li> + <LI>Next message: <A HREF="005973.html">[Mageia-dev] Firefox 5 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5971">[ date ]</a> + <a href="thread.html#5971">[ thread ]</a> + <a href="subject.html#5971">[ subject ]</a> + <a href="author.html#5971">[ 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> |