diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006025.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/006025.html | 133 |
1 files changed, 133 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006025.html b/zarb-ml/mageia-dev/2011-June/006025.html new file mode 100644 index 000000000..6ad907d08 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006025.html @@ -0,0 +1,133 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Update of backport, policy proposal + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Update%20of%20backport%2C%20policy%20proposal&In-Reply-To=%3C4E06F283.7020107%40eesti.ee%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006174.html"> + <LINK REL="Next" HREF="006030.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Update of backport, policy proposal</H1> + <B>Sander Lepik</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Update%20of%20backport%2C%20policy%20proposal&In-Reply-To=%3C4E06F283.7020107%40eesti.ee%3E" + TITLE="[Mageia-dev] Update of backport, policy proposal">sander.lepik at eesti.ee + </A><BR> + <I>Sun Jun 26 10:49:07 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006174.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI>Next message: <A HREF="006030.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6025">[ date ]</a> + <a href="thread.html#6025">[ thread ]</a> + <a href="subject.html#6025">[ subject ]</a> + <a href="author.html#6025">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>24.06.2011 03:15, Michael Scherer kirjutas: +><i> Hi, +</I>><i> +</I>><i> [ ... ] +</I>><i> +</I>><i> Last solution, declare that cherry picking is not supported, or that +</I>><i> people are on their own, and explain the reason. However, people have +</I>><i> been asking this, and recommend this. This would also be against a goal +</I>><i> of having confidence in the backports. +</I>><i> +</I>><i> +</I>><i> Again, and as said in the title, this is a proposal so feel free to +</I>><i> comment. +</I>><i> +</I>Reading comments here and knowing that our QA team is in trouble already - i don't see how +would QA handle backports. I can also see that there might come time when backports are +unpatched and thus unsecure. + +So i would say we can't support backports and when user installs package from backports it's +his/her problem to deal with it when there will be security holes or other problems. And +this should be very clear to everyone. + +I know we lack packages in mga1, so maybe we can push a little more to get those missing +packages working well but when most stuff is in mga2 we should continue with backports as +they are. We don't have QA nor packagers to keep all backports rock solid. + +-- +Sander + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006174.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI>Next message: <A HREF="006030.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6025">[ date ]</a> + <a href="thread.html#6025">[ thread ]</a> + <a href="subject.html#6025">[ subject ]</a> + <a href="author.html#6025">[ 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> |