diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006077.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/006077.html | 96 |
1 files changed, 96 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006077.html b/zarb-ml/mageia-dev/2011-June/006077.html new file mode 100644 index 000000000..3db47f7d0 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006077.html @@ -0,0 +1,96 @@ +<!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=%3C4E093215.4050901%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006030.html"> + <LINK REL="Next" HREF="006163.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Update of backport, policy proposal</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Update%20of%20backport%2C%20policy%20proposal&In-Reply-To=%3C4E093215.4050901%40laposte.net%3E" + TITLE="[Mageia-dev] Update of backport, policy proposal">andr55 at laposte.net + </A><BR> + <I>Tue Jun 28 03:44:53 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006030.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI>Next message: <A HREF="006163.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6077">[ date ]</a> + <a href="thread.html#6077">[ thread ]</a> + <a href="subject.html#6077">[ subject ]</a> + <a href="author.html#6077">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Sander Lepik a écrit : +><i> +</I>><i> 24.06.2011 03:15, Michael Scherer kirjutas: +</I> +[ ... ] + +><i> Reading comments here and knowing that our QA team is in trouble already +</I>><i> - i don't see how would QA handle backports. I can also see that there +</I>><i> might come time when backports are unpatched and thus unsecure. +</I> +The idea is to use the packager and backport requesters to test the backports, in place +of the QA team. This is considered adequate since backports would be "leaf" packages +(on which no other package is dependant), and so the packages need only be tested to +ensure that they work. +Of course for security issues, we have to be a little more careful. + +><i> -- +</I>><i> Sander +</I>><i> +</I> +-- +André +</PRE> + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006030.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI>Next message: <A HREF="006163.html">[Mageia-dev] Update of backport, policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6077">[ date ]</a> + <a href="thread.html#6077">[ thread ]</a> + <a href="subject.html#6077">[ subject ]</a> + <a href="author.html#6077">[ 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> |