diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016901.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016901.html | 131 |
1 files changed, 131 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016901.html b/zarb-ml/mageia-dev/2012-June/016901.html new file mode 100644 index 000000000..5c684d492 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016901.html @@ -0,0 +1,131 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Packagers meeting + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Packagers%20meeting&In-Reply-To=%3C4FEAE5D7.20903%40eesti.ee%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="016894.html"> + <LINK REL="Next" HREF="016902.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Packagers meeting</H1> + <B>Sander Lepik</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Packagers%20meeting&In-Reply-To=%3C4FEAE5D7.20903%40eesti.ee%3E" + TITLE="[Mageia-dev] Packagers meeting">sander.lepik at eesti.ee + </A><BR> + <I>Wed Jun 27 12:52:07 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016894.html">[Mageia-dev] Packagers meeting +</A></li> + <LI>Next message: <A HREF="016902.html">[Mageia-dev] Packagers meeting +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16901">[ date ]</a> + <a href="thread.html#16901">[ thread ]</a> + <a href="subject.html#16901">[ subject ]</a> + <a href="author.html#16901">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>27.06.2012 13:29, Thomas Backlund kirjutas: +><i> Well, technically yes, but as the purpose of this "carrot" is exactly +</I>><i> "if user want to get backports repos opened" then "user need to help +</I>><i> fix #2317 (or help find someone that can)" :) +</I>><i> +</I>><i> Point is that we are slowly killing QA, wich means at some point it will stop working -> +</I>><i> we might as well stop doing releases. +</I>I still don't understand where's the big problem if we enable release media for updates. +It's not updated, so it shouldn't slow down updating too much. Hardware that can run DEs +today should have no problems with release media enabled for updates. QA is proposing this +solution again and again. Is this really that hard to change? + +-- +Sander + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016894.html">[Mageia-dev] Packagers meeting +</A></li> + <LI>Next message: <A HREF="016902.html">[Mageia-dev] Packagers meeting +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#16901">[ date ]</a> + <a href="thread.html#16901">[ thread ]</a> + <a href="subject.html#16901">[ subject ]</a> + <a href="author.html#16901">[ 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> |