diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005979.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005979.html | 94 |
1 files changed, 94 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005979.html b/zarb-ml/mageia-dev/2011-June/005979.html new file mode 100644 index 000000000..9b96ff194 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005979.html @@ -0,0 +1,94 @@ +<!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=%3Cop.vxj30uern7mcit%40hodgins.homeip.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005975.html"> + <LINK REL="Next" HREF="005993.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Firefox 5</H1> + <B>David W. Hodgins</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Firefox%205&In-Reply-To=%3Cop.vxj30uern7mcit%40hodgins.homeip.net%3E" + TITLE="[Mageia-dev] Firefox 5">davidwhodgins at gmail.com + </A><BR> + <I>Fri Jun 24 03:35:08 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005975.html">[Mageia-dev] Firefox 5 +</A></li> + <LI>Next message: <A HREF="005993.html">[Mageia-dev] Firefox 5 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5979">[ date ]</a> + <a href="thread.html#5979">[ thread ]</a> + <a href="subject.html#5979">[ subject ]</a> + <a href="author.html#5979">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Thu, 23 Jun 2011 18:17:57 -0400, Ahmad Samir <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">ahmadsamir3891 at gmail.com</A>> wrote: + + +><i> Caveats: +</I>><i> - QA is too small, and it'll take time/effort to get through the +</I>><i> backported packages requiring tests, unless you depend on the user +</I>><i> asking for the backport to have tested the package properly, the user +</I>><i> will say it works if it works on his box for the arch he's using, he +</I>><i> won't do both archs, not just because he's lazy, but maybe he has one +</I>><i> Mageia box for example +</I>><i> - Sysadm team is already overworked with many other tasks, meaning the +</I>><i> packages requiring a move will rot for a while in backports_testing. +</I> +Once QA team members can push the packages from testing to updates or +backports, the sysadm team won't have to get involved. + +><i> Now compare that to what's used in e.g. mdv: +</I>><i> - User asks for a backport +</I>><i> - Packager submits the backport and closes the report +</I> +Just today, in alt.os.linux.mandriva, there was a user complaining that +firefox 4 wasn't available. When it was pointed out that it's been +in backports for quite a while, the response was that using backports +"broke" his system. Hopefully Mageia backports won't get that type +of reputation. One way to help with that, is to ensure that all +backports at least have some qa testing. + +I understand your concerns. + +My proposal is to use the backports testing, and see if the qa team +can keep up. If not, having the package pushed directly from cauldron +to backports, or release/updates could be opened up later. Nothing +is being fixed in stone here. + +Regards, Dave Hodgins +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005975.html">[Mageia-dev] Firefox 5 +</A></li> + <LI>Next message: <A HREF="005993.html">[Mageia-dev] Firefox 5 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5979">[ date ]</a> + <a href="thread.html#5979">[ thread ]</a> + <a href="subject.html#5979">[ subject ]</a> + <a href="author.html#5979">[ 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> |