diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-October/009192.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-October/009192.html | 172 |
1 files changed, 172 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-October/009192.html b/zarb-ml/mageia-dev/2011-October/009192.html new file mode 100644 index 000000000..a86e6931f --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/009192.html @@ -0,0 +1,172 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Subrel for version updates on stable releases + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Subrel%20for%20version%20updates%20on%20stable%20releases&In-Reply-To=%3C4EABD0AC.8050402%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="009187.html"> + <LINK REL="Next" HREF="009194.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Subrel for version updates on stable releases</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Subrel%20for%20version%20updates%20on%20stable%20releases&In-Reply-To=%3C4EABD0AC.8050402%40laposte.net%3E" + TITLE="[Mageia-dev] Subrel for version updates on stable releases">andre999mga at laposte.net + </A><BR> + <I>Sat Oct 29 12:08:44 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="009187.html">[Mageia-dev] Subrel for version updates on stable releases +</A></li> + <LI>Next message: <A HREF="009194.html">[Mageia-dev] Subrel for version updates on stable releases +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9192">[ date ]</a> + <a href="thread.html#9192">[ thread ]</a> + <a href="subject.html#9192">[ subject ]</a> + <a href="author.html#9192">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Samuel Verschelde a écrit : +><i> Le vendredi 28 octobre 2011 18:17:18, Anssi Hannula a écrit : +</I>><i> +</I>>><i> Hi! +</I>>><i> +</I>>><i> Currently the updates policy [1] says that updates to a new version +</I>>><i> should have 1.1.mga1 as release, and that cauldron should be bumped to +</I>>><i> 2.mga2 on those cases. +</I>>><i> +</I>>><i> However, on the packages where version updates are done (e.g. wine, +</I>>><i> flash-player-plugin, opera, firefox, chromium), doing that causes the +</I>>><i> following chain of events on every update: +</I>>><i> +</I>>><i> 1. cauldron submission with 1.mga2 +</I>>><i> 2. mga1 submission with 1.1.mga1 +</I>>><i> 3. cauldron submission with 2.mga2 +</I>>><i> +</I>>><i> So the pkgs have to always be submitted to cauldron twice (unless one +</I>>><i> skips right to 2.mga2, which would be rather confusing IMO). +</I>>><i> +</I>>><i> I suggest we change the policy to say that package updates to stable +</I>>><i> should use 1.mga1 release (i.e. no subrel), so that it goes: +</I>>><i> 1. cauldron submission with 1.mga2 +</I>>><i> 2. mga1 submission with 1.mga1 +</I>>><i> +</I>>><i> and no extra submissions or commits required. +</I>>><i> +</I>>><i> Then, if some extra fix is needed, one does: +</I>>><i> 1. cauldron submission with 2.mga2 +</I>>><i> 2. mga1 submission with 1.1.mga1 +</I>>><i> +</I>>><i> +</I>>><i> WDYT? +</I>>><i> +</I>>><i> [1] <A HREF="http://www.mageia.org/wiki/doku.php?id=updates_policy">http://www.mageia.org/wiki/doku.php?id=updates_policy</A> +</I>>><i> +</I>><i> I warned about this when we discussed about release 0 and subrels for updates, +</I>><i> but nobody reacted against at that time, so it ended in the written policy :) +</I>><i> +</I>><i> See <A HREF="https://mageia.org/pipermail/mageia-dev/2011-July/007080.html">https://mageia.org/pipermail/mageia-dev/2011-July/007080.html</A> +</I>><i> +</I>><i> I don't see drawbacks to your change proposal, if no one does, it gets my +</I>><i> vote. +</I>><i> +</I>I agree as well. No sense in useless rebuilding. + +Sometimes the version in cauldron is only an upstream bugfix to the +version in stable. +It that case, it is the only logical thing to do. +Since except for the versioning, the builds in cauldron and stable would +be identical. + +That is the case for xkeyboard-config, where version 2.3 in cauldron is +an upstream bugfix for version 2.2 in mga1 +(<A HREF="https://bugs.mageia.org/show_bug.cgi?id=2280">https://bugs.mageia.org/show_bug.cgi?id=2280</A>) + +I noticed that that was also essentially the case for a recent bug with +hunspell, even though upstream had bumped the major release number. +(<A HREF="https://bugs.mageia.org/show_bug.cgi?id=2272">https://bugs.mageia.org/show_bug.cgi?id=2272</A>) +(Actually several upstream updates, one with an alternate release +major/minor designations. Essentially bugfix updates.) +So a lot of effort was made to provide an update by patches to fix a +bug, when just using the update in cauldron would have satisfied the +problem. With no risk of regression, since the requires were identical, +and many if not most of the dependant localisations were identical as well. +I'm not sure if the current policy, as written, prevents using the +version from cauldron as an update to stable, when the major/minor +release numbers differ. +Would be good to clarify / modify if necessary. +><i> Best regards +</I>><i> +</I>><i> Samuel Verschelde +</I>><i> +</I> +Regards :-) + +-- +André + +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="009187.html">[Mageia-dev] Subrel for version updates on stable releases +</A></li> + <LI>Next message: <A HREF="009194.html">[Mageia-dev] Subrel for version updates on stable releases +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#9192">[ date ]</a> + <a href="thread.html#9192">[ thread ]</a> + <a href="subject.html#9192">[ subject ]</a> + <a href="author.html#9192">[ 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> |