The German translation of "mirror" in MCC --> Sources is wrong. It says "Speigel", but is supposed to say "Spiegel".
Already fixed ins svn.
I am sorry, but why is this not being included in the updates? I mean, it's all nice and well that it is fixed in svn, but that is quite irrelevant if the users don't get the updates that fix that in the actual distribution. I mean, this has been "fixed" for 2 1/2 months now, shouldn't it somehow make its way to the users?
Btw: Bugs shouldn't be marked as fixed as long as they aren't actually fixed for the users!
It is fixed in svn, so from the point of view of the people in charge (German i18n team in this case) it is resolved as fixed.
The other question is: Why was there no update for the end user of Mageia 1?
Now I'm quite sure this is an error making the system unusable for the majority of people, thus being of the utmost importance for building an updated package, since literally any German stumbling upon it will have nights of nightmares because of it
Now in my opinion this is just a little - even funny looking - typo, that has no importance whatsoever for anybody, so I think there is no need just to correct this.
Leaving this opened with the lowest priority...
I guess the question is: When is a fix important enough to warrant an update?
In this case, seeing how this is an obvious typo that is only visible to German users, I tend to say that no update is needed if there are no other things to fix. On the other hand, looking at a typo for more than a year isn't very nice either.
Perhaps we need to have a seperate class of 'trivial' bugs like these? They might be pushed to updates without qa validation and/or without an update advisory sent out.
My opinion is we should fix this kind of small bug in Mageia 1 SVN (currently it's only fixed in cauldron's SVN), but not issue an update for now. If in the future we need to issue an update for an important bugfix, this small fix will be included with it.
This would also mean that, in the updates process, we should always look at SVN history to see what bug fixes have been done and are waiting for delivery.
Remco's suggestion of an update pushed wihtout QA validation will never be done, because we never know : a simple fix could break something (even if I doubt it), and most of all a new build of the package can introduce regressions, rarely, but the risk is enough that we can't push an update without testing.
Of course this is a very minor "bug" by itself. But (as Remco already pointed out) seeing such a small thing not being fixed for months gives a wrong impression to people who evaluate the distribution not only by the looks and the number of packages but also by the bug fixing performance.
What kind of risk is an update if the only change is a typo in the translation of a menue item? As much as I agree to the rather safe approach of Mageia wrt updates, this is a bit too "careful", IMHO.
May I also point out that we got feedback from people who think there are too much updates? Forcing an update to all Mageia users just for a typo in German translations would be too much, in my opinion.
That's why I think we must try to group several bug fixes into a single update, whenever possible. It saves work for everybody involved (issueing an update needs work from several people, it's not just "fix and push") and makes less updates to download for users.
That's why I proposed that we fix it, but wait for the next update of rpmdrake (I'm sure there are open bugs that can deserve an update) to push it.
What about calling for an i18n Bug hunting Day and doing an overall draktools update in a few weeks?
Why not, if the drakxtools maintainers agree :)
(In reply to comment #8)
> What about calling for an i18n Bug hunting Day and doing an overall draktools
> update in a few weeks?
cc'ing you because of this idea of Oliver. Maybe this day can be scheduled along with the bug fixing days you had in mind ;)
still rpmdrake-5.26.10-1.mga1, no new version, so not fixed
(In reply to comment #11)
> still rpmdrake-5.26.10-1.mga1, no new version, so not fixed
fixed in Mageia 2, though ;)
Minor issue that is not sufficient to rebuild rpmdrake for 1.
Fixed in 2 and Cauldron.