diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/006045.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/006045.html | 96 |
1 files changed, 96 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/006045.html b/zarb-ml/mageia-dev/2011-June/006045.html new file mode 100644 index 000000000..80974c137 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/006045.html @@ -0,0 +1,96 @@ +<!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=%3C4E074976.5000504%40iki.fi%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="006019.html"> + <LINK REL="Next" HREF="006047.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=%3C4E074976.5000504%40iki.fi%3E" + TITLE="[Mageia-dev] Backports policy proposal">anssi.hannula at iki.fi + </A><BR> + <I>Sun Jun 26 17:00:06 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="006019.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI>Next message: <A HREF="006047.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6045">[ date ]</a> + <a href="thread.html#6045">[ thread ]</a> + <a href="subject.html#6045">[ subject ]</a> + <a href="author.html#6045">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 26.06.2011 01:34, Michael Scherer wrote: +><i> Le vendredi 24 juin 2011 à 17:33 +0300, Anssi Hannula a écrit : +</I>>><i> On 24.06.2011 03:10, Michael Scherer wrote: +</I>>>><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>>><i> +</I>>><i> So this will prevent backporting anything to mga1 if it is not in mga2 +</I>>><i> release/updates ? +</I>><i> +</I>><i> That's a good question but yes, I would consider such policy. +</I>><i> Ie, do backport only for the latest supported release. +</I> +This will essentially prevent backporting anything to mga1 after mga2 +release. :/ + +-- +Anssi Hannula +</PRE> + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="006019.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI>Next message: <A HREF="006047.html">[Mageia-dev] Backports policy proposal +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#6045">[ date ]</a> + <a href="thread.html#6045">[ thread ]</a> + <a href="subject.html#6045">[ subject ]</a> + <a href="author.html#6045">[ 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> |