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/009190.html | 141 ++++++++++++++++++++++++++++ 1 file changed, 141 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-October/009190.html (limited to 'zarb-ml/mageia-dev/2011-October/009190.html') diff --git a/zarb-ml/mageia-dev/2011-October/009190.html b/zarb-ml/mageia-dev/2011-October/009190.html new file mode 100644 index 000000000..7af9b9dbd --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/009190.html @@ -0,0 +1,141 @@ + + + + [Mageia-dev] Subrel for version updates on stable releases + + + + + + + + + +

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

+ D.Morgan + dmorganec at gmail.com +
+ Sat Oct 29 01:38:03 CEST 2011 +

+
+ +
On Fri, Oct 28, 2011 at 11:32 PM, Anssi Hannula <anssi at mageia.org> wrote:
+> On 28.10.2011 20:07, D.Morgan wrote:
+>> On Fri, Oct 28, 2011 at 6:17 PM, Anssi Hannula <anssi at mageia.org> wrote:
+>>> 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
+>>>
+>>> --
+>>> Anssi Hannula
+>>>
+>>
+>>
+>> Why not simple 0.1mga1 in updates  ? because if we add a fix in mageia
+>> again we will have to rebuild in cauldron anyway but if we use
+>
+> If a fix is added in mageia1 again, the same fix needs to be added in
+> cauldron always as well.
+
+you get a point here :)
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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