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/2012-January/011224.html | 108 ++++++++++++++++++++++++++++ 1 file changed, 108 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-January/011224.html (limited to 'zarb-ml/mageia-dev/2012-January/011224.html') diff --git a/zarb-ml/mageia-dev/2012-January/011224.html b/zarb-ml/mageia-dev/2012-January/011224.html new file mode 100644 index 000000000..3fb237d6d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/011224.html @@ -0,0 +1,108 @@ + + + + [Mageia-dev] please stop doing "bugs" for updating magia 1 + + + + + + + + + +

[Mageia-dev] please stop doing "bugs" for updating magia 1

+ Florian Hubold + doktor5000 at arcor.de +
+ Wed Jan 11 09:43:33 CET 2012 +

+
+ +
Am 11.01.2012 08:57, schrieb Buchan Milne:
+> On Wednesday, 11 January 2012 06:32:50 Johnny A. Solbu wrote:
+>> On Wednesday 11 January 2012 03:28, Luis Daniel Lucio Quiroz wrote:
+>>> I mean, stop asking updates for mageia 1 just because there is another
+>>> newversion.
+>> May I suggest that next time, say it in so many words.
+>>
+>> Some of us are not good at reading between the lines, and your original
+>> post was written in a way that indicated that it was not clear on that you
+>> where talking about just what you said you where talking about in your
+>> last post. :-)=
+>>
+>>
+>> And I agree with you. Updating packages in a released product just because
+>> a new version is out is not a valid reason by itself. If on the other hand
+>> it fixes some bugs or security holes, it's worth considering.
+> Resolving the backports situation would however provide a means for users who 
+> want to track upstream (for various reasons, such as being able to get support 
+> from upstreams who don't really want to support 'historic' releases) without:
+> 1)Forcing all users to get the update
+> 2)Requiring excessive QA work
+> 3)Requiring bug reports for each update
+Well, 2) and 3) are not valid reasons here, because backports should get
+a similar amount of QA testing as normal update candidates, and for
+the updates policy require a bugreport for validation through QA.
+Check https://wiki.mageia.org/en/Backports_policy#Steps
+and https://wiki.mageia.org/en/Updates_policy
+> Regards,
+> Buchan
+>
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+

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