Re: Time for translation to get into stable release
-----BEGIN PGP SIGNED MESSAGE-----
On 2016-12-20 10:56, Andrey Skvortsov wrote:
> On 16-12-20 09:23, helix84 wrote:
>> That's up to the maintainer of each individual package. First and
>> foremost, unless you're translating a package that appears only
>> in Debian or debconf templates of a package, you really should
>> send your translation to the upstream package where it will
>> appear in the next upstream release. Then you need to wait for
>> the debian package maintainer (won't hurt to ping them) to
>> package that upstream release. Whether that package version is
>> part of Stretch will depend on the freeze deadlines  (full
>> freeze for updates to existing packages).
> Previously I thought that the best approach would be to report a
> bug against Debian package with new/updated translation attached
> and package maintainer will forward it to the upstream project. In
> this case Debian will get all translation even if next upstream
> release is going to miss Debian release.
This is mostly luck rather than rule. If you submit a translation to
debian and it is not included in the upstream/original project the
package maintainer need to care for the local change until it is
included and that's typically things a maintainer will avoid (by good
Translations of individual applications are better done at the
original project because by that it will benefit all users not only
Debian and their downstreams (Ubuntu et al). It will also be easier to
integrate updates to the translations into the release process of the
> But apparently my understanding of workflow is wrong. Is it?
There are no single Debian Workflow[tm], every pakcage maintainer can
use what ever tools and workflows they like.
The above addresses applications documentation and manual pages et al.
For debian specific things like debconf questions, release notes,
installation guide and other things there are best practices that can
be boiled down to time frames and schedules but evertyhing need to fit
into the package mantainers schedule at last.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----