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

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

+ Antoine Pitrou + solipsis at pitrou.net +
+ Wed Jan 11 17:43:35 CET 2012 +

+
+ +
On Wed, 11 Jan 2012 16:51:55 +0100
+Guillaume Rousse
+<guillomovitch at gmail.com> wrote:
+> Le 11/01/2012 16:09, Antoine Pitrou a écrit :
+> > As a Mageia user I would expect Mageia to package significant *bugfix
+> > releases* and ship them in the updates for the stable distro.
+> You'd rather read the current update policy, rather than expect blind 
+> assertions:
+> https://wiki.mageia.org/en/Updates_policy
+
+Thanks.
+
+> > For example, it would be nice if an up-to-date Mageia 1 system had
+> > Python 2.7.2 rather than Python 2.7.1 (not a deal-breaker, of course,
+> > but nice). There's more than a hundred bug fixes between the two
+> > versions and I don't expect Mageia to have independently fixed many of
+> > these bugs.
+> A bug may vary from a typo in a man page to a critical security update, 
+> which make the number of claimed bugfix a poor decision metric. A 
+> non-regression ensurance would be a better one, but it's quite difficult 
+> to assert.
+
+As both an user and an upstream developer, I would not expect a Mageia
+packager to know better than the upstream developers what can
+constitute a regression, and what is a good compromise to fix or not.
+At least for well-maintained upstream projects, that is :-)
+
+> Welcome to our new QA team volonteer :)
+
+Agreed that my advice would be more constructive if I got involved, but
+I don't have the time for that.
+
+Regards
+
+Antoine.
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + + +
+

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