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

[Mageia-dev] Updates and 0 release

+ Anssi Hannula + anssi.hannula at iki.fi +
+ Tue Jul 26 18:27:48 CEST 2011 +

+
+ +
On 26.07.2011 19:20, Colin Guthrie wrote:
+> 'Twas brillig, and Michael Scherer at 26/07/11 11:40 did gyre and gimble:
+>> If the goal is to be sure that the software is still upgradable, the
+>> whole %mkrel stuff should take care of that.
+> 
+> No it doesn't. That only works for one release assuming we do not use
+> subrel with that release. Even with mkrel, we will instantly need to
+> bump the cauldron package as soon as it's used for the first time.
+
+If one does another update (i.e. adds subrel), it should mean that the
+fixes/whatever have been done to the cauldron tree first and thus
+cauldron has 1.0-2.mga1, while mga1 gets 1.0-1.1.mga1.
+
+> We used to do 0 releases in Mandriva quite often, and I don't think this
+> is necessarily problematic. If a package is a prerelease, the release
+> itself will likely contain the word git or svn etc.
+> 
+> Col
+> 
+> 
+
+
+-- 
+Anssi Hannula
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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