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-August/007657.html | 112 +++++++++++++++++++++++++++++ 1 file changed, 112 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-August/007657.html (limited to 'zarb-ml/mageia-dev/2011-August/007657.html') diff --git a/zarb-ml/mageia-dev/2011-August/007657.html b/zarb-ml/mageia-dev/2011-August/007657.html new file mode 100644 index 000000000..56d14fc5f --- /dev/null +++ b/zarb-ml/mageia-dev/2011-August/007657.html @@ -0,0 +1,112 @@ + + + + [Mageia-dev] Tiny cosmetic fixes + + + + + + + + + +

[Mageia-dev] Tiny cosmetic fixes

+ andre999 + andre999.mga at laposte.net +
+ Mon Aug 29 21:18:47 CEST 2011 +

+
+ +
Remco Rijnders a écrit :
+> Hi all,
+>
+> The topic came up what to do with small cosmetic fixes in packages which
+> are part of the official release. See for instance the following bug
+> report: https://bugs.mageia.org/show_bug.cgi?id=1784
+>
+> Should we push these things as an update (and spending GB's of bandwidth
+> for all the upgrades) or leave them as is (and thereby perhaps annoying
+> the eyeballs of the users affected?)
+>
+> Any thoughts?
+>
+> Thanks,
+>
+> Remco
+
+Since such cases are
+(1) trivial in terms of risk (in this case an incorrect translation), with no 
+functional effect on other packages, and
+(2) correct esthetically negative problems for the users affected (in this case 
+german-language users of the package in question)
+
+it seems most appropriate to
+(1) have a minimal QA for the change, and
+(2) push the package with a low (lowest) priority
+
+That way, we don't (significantly) impact the build system, and we don't leave 
+users with up to 9 months of (minor) dysfunction.
+
+-- 
+André
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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