2010/11/20 Lior Kaplan <kaplanl...@gmail.com>: > >> Translations can be committed any time to libreoffice-3-3 branch, when >> someone asks explicitly. >> >> > I would prefer to have this done on a deadline we choose for translations, > and not in a sporadic way.
Why? People might want to build themselves and want their latest translations included. There are only 10-15 active languages, we can handle it in the sporadic way, too. > > On the deadline we could take all the translations from master branch on git > and the pootle and make > sure they're committed to the 3.3 branch. > The entire "build" repository including lo-build* files will be removed very soon from master. We should not use master for 3.3 translations. > I guess it's time to develop the translation process as part of the release > process. I'm not sure who to work with on this ? It's the best if we don't wait for somebody else, but start to find out how to work. We don't need a complicated process, because it will be used only once (only for 3.3). A few teams have already updated their data on http://wiki.documentfoundation.org/Translation_for_3_3. When we have a deadline, all po files from the teams who have YES in their Pootle column should be committed to git (libreoffice-3-3 branch). If the team has NO or nothing in their Pootle column, then it will be the responsibility of the language team leader to send their translation to this list by the deadline. Translations may come from Novell/openSUSE as well, as the did in the past. Ideally it will not interfere with our work, i.e. they work on only those languages which we don't work on. How can we make sure? Petr? Thanks, Andras -- E-mail to l10n+h...@libreoffice.org for instructions on how to unsubscribe List archives are available at http://www.libreoffice.org/lists/l10n/ All messages you send to this list will be publicly archived and cannot be deleted
