hi everybody, looking forward to the release of 2.2, i notice how many translation issues that were targetted to 2.1 have been postponed again (sometimes for more than one release cycle). i thought of the idea if somewhere at the beginning of the 2.3.x development everybody would be "urged" to solve string translation bugs (perhaps one or two weeks after a call for easy patches by volunteers has been posted on the lists and on the blog at the beginning of 2.3 development, so that the novell employees do not have to work out *every* of those shitty bugs). i'm thinking of this because *many* translation bugs were tried to get solved only a few days before string freeze toke place and even more became inevitably postponed by the string freeze once again. :-/ atm open string translation issues are all remaining dependencies of bugs 46224 and 36276; bugs 41909, 71523, 72242, 61736, 72464, 72518, 70376 and all those i haven't found yet. ;-) another great thing would be to review and to force decisions on open bugs with keyword "patch" since obviously the code base changes the older the patch gets... evo, eds, gal, gtkhtml alltogether have more than 100 open bugs with "patch" keyword waiting for decisions, so with both issues addressed, the bug database would be heavily cleaned. comments? [hmmm... just thinking if posting in the last days of 2.1.x and on saturdays reduces feedback, i hope it does not :-) ] cheers, andre -- mailto:ak-47 gmx net | failed! http://www.iomc.de
Attachment:
signature.asc
Description: This is a digitally signed message part