diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005995.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005995.html | 115 |
1 files changed, 115 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005995.html b/zarb-ml/mageia-dev/2011-June/005995.html new file mode 100644 index 000000000..04cf78d14 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005995.html @@ -0,0 +1,115 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Backports 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%20Backports%20policy%20proposal&In-Reply-To=%3C4E04A04D.7070903%40iki.fi%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006005.html"> + <LINK REL="Next" HREF="006019.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Backports policy proposal</H1> + <B>Anssi Hannula</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20proposal&In-Reply-To=%3C4E04A04D.7070903%40iki.fi%3E" + TITLE="[Mageia-dev] Backports policy proposal">anssi.hannula at iki.fi + </A><BR> + <I>Fri Jun 24 16:33:49 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006005.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI>Next message: <A HREF="006019.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5995">[ date ]</a> + <a href="thread.html#5995">[ thread ]</a> + <a href="subject.html#5995">[ subject ]</a> + <a href="author.html#5995">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 24.06.2011 03:10, Michael Scherer wrote: +><i> Another rule that we could add is that cauldron should always be newer +</I>><i> than backports, in order to ensure upgradability. The same goes for n-2 +</I>><i> and n-1 release. +</I>><i> While this seems innocent, do not forget this will have a impact when we +</I>><i> do the version freeze. +</I> +So this will prevent backporting anything to mga1 if it is not in mga2 +release/updates ? + +Also, I don't see the advantage in preventing backports during freeze. +The backports are re-allowed soon anyway, and the upgradeability goes +away anyway. + +-- +Anssi Hannula +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006005.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI>Next message: <A HREF="006019.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5995">[ date ]</a> + <a href="thread.html#5995">[ thread ]</a> + <a href="subject.html#5995">[ subject ]</a> + <a href="author.html#5995">[ 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> |