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

[Mageia-dev] Updates and 0 release

+ Sander Lepik + sander.lepik at eesti.ee +
+ Tue Jul 26 14:07:51 CEST 2011 +

+
+ +
26.07.2011 13:40, Michael Scherer kirjutas:
+> Hi,
+>
+> while trying to work on the queue of update needing a push, I noticed
+> that almost all of them use a "Release: 0".
+>
+> Since this has a specific meaning ( ie, used for pre release, or svn
+> snapshot ), using this for updates is quite confusing, and I do not see
+> the reason for that.
+>
+> If the goal is to be sure that the software is still upgradable, the
+> whole %mkrel stuff should take care of that. And if not, we can rebuild
+> in cauldron to increase the release.
+Can someone please update the policy 
+(http://mageia.org/wiki/doku.php?id=updates_policy) then. If following 
+policy gets you unvalidated then something IS wrong.
+
+--
+Sander
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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