2009/5/21 Gerhard Killesreiter <gerhard@killesreiter.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andriy Podanenko schrieb:

Hi Andriy!

> Didn`t found it in docs (may be bad looking 8( )

> When I commited translations into per module translations directory for all
> possible branches(DRUPAL-X--X not revisions like DRUPAL-X--X-BETAX (no
> access)) - are there any automation script for integrating those
> translations into module releases?Or this process only human based and I
> have to post issues to all translated modules for getting access to modules
> CVS or pinging module developers for including translations into feature
> releases?

You translations will only be integrated into future releases. You
need to commit the translation to the branch the module author is
working on, say DRUPAL-6--1, and the next time the author will create
a tag on that branch and make a release on that tag, your translations
will be included.

Cheers,

Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkoVOsAACgkQfg6TFvELooSPuACfUIuvm39np4TvvVgly6K2mnsF
QjAAniD3MsogKtICGWZ2l6jpDQ9K8rvc
=laII
-----END PGP SIGNATURE-----
_______________________________________________
translations mailing list
translations@drupal.org
http://lists.drupal.org/mailman/listinfo/translations