diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101006/000870.html')
-rw-r--r-- | zarb-ml/mageia-dev/20101006/000870.html | 85 |
1 files changed, 85 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101006/000870.html b/zarb-ml/mageia-dev/20101006/000870.html new file mode 100644 index 000000000..0655554db --- /dev/null +++ b/zarb-ml/mageia-dev/20101006/000870.html @@ -0,0 +1,85 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] How will be the realese cycle? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3CPine.LNX.4.44.1010060031050.20026-100000%40outpost-priv%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000869.html"> + <LINK REL="Next" HREF="000871.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How will be the realese cycle?</H1> + <B>Tux99</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20will%20be%20the%20realese%20cycle%3F&In-Reply-To=%3CPine.LNX.4.44.1010060031050.20026-100000%40outpost-priv%3E" + TITLE="[Mageia-dev] How will be the realese cycle?">tux99-mga at uridium.org + </A><BR> + <I>Wed Oct 6 00:39:09 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="000869.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="000871.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#870">[ date ]</a> + <a href="thread.html#870">[ thread ]</a> + <a href="subject.html#870">[ subject ]</a> + <a href="author.html#870">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, 6 Oct 2010, nicolas vigier wrote: + +><i> > I think you misunderstood the concept proposed, we are not talking about +</I>><i> > replacing cooker/cauldron, just merging updates and backports for the +</I>><i> > released version. +</I>><i> +</I>><i> And then you run "urpmi --auto-select" on your server, and all your web +</I>><i> sites stop working because php was updated to a new version which is not +</I>><i> 100% compatible with the previous one ... +</I> +Hmm, two things, actually three: + +1) I'd never use Mandriva on a server, because of the short support +period, a server OS requires at least 4-5 years support lifecycles +(I'm not talking about MES here, just the normal Mandriva variants) + +2) from my experience "urpmi --auto-select" does that anyway, it doesn't +seem to differentiate between updates and backports (unlike drakrpm that +correctly ignores backports when checking for updates) + +3) I mentioned earlier that the packager would need to use good +judgement and not include major incompatible version changes + +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000869.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI>Next message: <A HREF="000871.html">[Mageia-dev] How will be the realese cycle? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#870">[ date ]</a> + <a href="thread.html#870">[ thread ]</a> + <a href="subject.html#870">[ subject ]</a> + <a href="author.html#870">[ 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> |