From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2011-October/009187.html | 141 ++++++++++++++++++++++++++++ 1 file changed, 141 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-October/009187.html (limited to 'zarb-ml/mageia-dev/2011-October/009187.html') diff --git a/zarb-ml/mageia-dev/2011-October/009187.html b/zarb-ml/mageia-dev/2011-October/009187.html new file mode 100644 index 000000000..635361b80 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/009187.html @@ -0,0 +1,141 @@ + + + + [Mageia-dev] Subrel for version updates on stable releases + + + + + + + + + +

[Mageia-dev] Subrel for version updates on stable releases

+ Samuel Verschelde + stormi at laposte.net +
+ Fri Oct 28 23:06:22 CEST 2011 +

+
+ +
Le vendredi 28 octobre 2011 18:17:18, Anssi Hannula a écrit :
+> Hi!
+> 
+> Currently the updates policy [1] says that updates to a new version
+> should have 1.1.mga1 as release, and that cauldron should be bumped to
+> 2.mga2 on those cases.
+> 
+> However, on the packages where version updates are done (e.g. wine,
+> flash-player-plugin, opera, firefox, chromium), doing that causes the
+> following chain of events on every update:
+> 
+> 1. cauldron submission with 1.mga2
+> 2. mga1 submission with 1.1.mga1
+> 3. cauldron submission with 2.mga2
+> 
+> So the pkgs have to always be submitted to cauldron twice (unless one
+> skips right to 2.mga2, which would be rather confusing IMO).
+> 
+> I suggest we change the policy to say that package updates to stable
+> should use 1.mga1 release (i.e. no subrel), so that it goes:
+> 1. cauldron submission with 1.mga2
+> 2. mga1 submission with 1.mga1
+> 
+> and no extra submissions or commits required.
+> 
+> Then, if some extra fix is needed, one does:
+> 1. cauldron submission with 2.mga2
+> 2. mga1 submission with 1.1.mga1
+> 
+> 
+> WDYT?
+> 
+> [1] http://www.mageia.org/wiki/doku.php?id=updates_policy
+
+I warned about this when we discussed about release 0 and subrels for updates, 
+but nobody reacted against at that time, so it ended in the written policy :)
+
+See https://mageia.org/pipermail/mageia-dev/2011-July/007080.html
+
+I don't see drawbacks to your change proposal, if no one does, it gets my 
+vote.
+
+Best regards
+
+Samuel Verschelde
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1