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-July/007056.html | 112 +++++++++++++++++++++++++++++++ 1 file changed, 112 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-July/007056.html (limited to 'zarb-ml/mageia-dev/2011-July/007056.html') diff --git a/zarb-ml/mageia-dev/2011-July/007056.html b/zarb-ml/mageia-dev/2011-July/007056.html new file mode 100644 index 000000000..de1efc5a4 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/007056.html @@ -0,0 +1,112 @@ + + + + [Mageia-dev] Updates and 0 release + + + + + + + + + +

[Mageia-dev] Updates and 0 release

+ Samuel Verschelde + stormi at laposte.net +
+ Wed Jul 27 12:52:04 CEST 2011 +

+
+ +
Le mardi 26 juillet 2011 19:38:30, Samuel Verschelde a écrit :
+> Le mardi 26 juillet 2011 18:42:05, Michael Scherer a écrit :
+> [snip]
+> 
+> > Yet, the problem would also be there for regular non-version upgrade
+> > ( ie, if we have foo-2-2.mga2 in cauldron and stable, and that we need
+> > to rebuild on stable and not on cauldron, we face the same problem ), so
+> > using 0 is a incomplete solution to the issue, and the only solution is
+> > to rebuild in cauldron, and such problem should better be detected by
+> > youri.
+> 
+> Very good point, this is a decisive argument to me.
+> 
+> > So, the conclusion is that we should test ugprade rather than assuming
+> > that it will just work because we placed a 0 instead of a 1 somewhere.
+> 
+> Ok for me provided we put in place the necessary processes to avoid upgrade
+> problems (Youri::Submit::Test::Precedence for example).
+> 
+> > Now, using 0 prevent us from having a simple way of seeing what
+> > prerelease we ship and that should be updated to latest stable ( as this
+> > seems to me quite desirable ).
+> 
+> Good point too.
+> 
+> > This is also inconsistent with the practice we had of backporting from
+> > cooker ( as the initial goal at Mandriva was to have 0 modifications
+> > from cooker to backports to reduce the load ). And if we ship something
+> > in update and in backports, we would have the same packages with 2
+> > different releases, and that doesn't seems a good idea.
+> 
+> Worse, the backport would be preferred to the update :/
+> 
+> You should have said all this right from the start rather than assuming
+> that we would have all these elements in mind :)
+> 
+> Samuel
+
+I suggest we add this point to tonight's meeting topics and that a decision be 
+taken then.
+
+Then we would adapt the updates policy and the current packages in 
+updates_testing if the 0 release in updates is abandoned. We must also decide 
+if we continue to use subrels or not (using them could avoid unneeded rebuilds 
+in cauldron when there are packaging bugs in updates).
+
+Best regards
+
+Samuel
+
+ + + + + + + + + + +
+

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