[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: postfixadmin 2.3.5-1: Please translate debconf PO for the package postfixadmin



Christian PERRIER <bubulle@debian.org> writes:

> Quoting Helge Kreutzmann (debian@helgefjell.de):
>> On Wed, Apr 11, 2012 at 10:11:40AM -0400, David Prévot wrote:
>> > Le 11/04/2012 05:06, Gergely Nagy a écrit :
>> > 
>> > > I would like to ask everyone involved - maintainers and translators
>> > > alike - to not do that: don't request bugs to be filed against packages
>> > > not yet in the archive, and preferably don't file bugs against such
>> > > stuff. Send translations to the maintainer directly instead, or get the
>> > > package in the archive first - whatever works for you, but what happend
>> > > here is a tiny bit annoying for everyone involved.
>> > 
>> > Sure, it's pretty rare that maintainers care enough for translations to
>> > ask for them before the package actually enters the Debian archive, I
>> > would like to first thank Norman for that. In such case, we should
>> > indeed care to handle the bugs properly, but asking translators to *not*
>> > fill bug report is a bit tough. Those bugs report are quite easy to
>> > find:
[...]
> Sre, but I don't thing that Gergely wa in any way trying to discourage
> people to consider localization the way it should be.
>
> What happened here is just infortunate : we have a motivated
> maintainer who really wants to do things The Right Way, he calls for
> translations and, unfortunately, uses the standard template for tis,
> that encourages sending bug reports.
>
> And we have QA people who are processing bugs sent to unknown
> packages, which is something I guess is a very tedious task. I suppose
> that Gergely was just slightly annoyed by seeing us translators (me
> included!) blindly sending bu reports against an unknown package.

Indeed, this is the case. Filing bugs for translations is great, and a
practice that I think works very well. But when a package is not in the
archive, the BTS has no idea where to forward the reports to, so they
don't reach the maintainer, and he won't receive the translations you
prepared for him.

Unless, of course, he goes back to check the bug reports, but that's not
all that convenient, in my opinion.

Also, once the package is uploaded, it will be properly associated with
the bug reports already filed, BUT it will at least look interesting
that the bugs are filed against AND fixed in the same version. I do not
know if that has any ill side effects, but it's certainly weird.

Anyhow, I think the message went through - and cases like this are rare
enough anyway.

Thanks for your work, and your time, keep it up!

-- 
|8]


Reply to: