Trac is being migrated to new services! Issues can be found in our new YouTrack instance and WIKI pages can be found on our website.

Changes between Version 66 and Version 67 of ReleaseProcess


Ignore:
Timestamp:
Feb 1, 2014, 10:41:10 PM (10 years ago)
Author:
MarkDoliner
Comment:

New steps for getting updated translations.

Legend:

Unmodified
Added
Removed
Modified
  • ReleaseProcess

    v66 v67  
    1010 1. Send an email to translators@pidgin.im and devel@pidgin.im announcing the string freeze.
    1111
    12 = Pre Release =
    13  1. Commit pending translation updates from [query:?status=new&type=translation&order=priority our Trac] and [https://www.transifex.com/projects/p/pidgin/resources/ Transifex] (it's possible that only Mark and Richard are able to get translations from Transifex--create an account and talk to them if you want access).  Remember to strip location info from them before committing as described in TipsForTranslators.  And it's good to test for mismatched c-format specifiers: "`msgfmt -cv NN`"
     12= Pre-Release =
     13== Commit Updated Translations ==
     14'''Background'''[[br]]
     15Transifex is configured to automatically pull pidgin.pot from https://developer.pidgin.im/l10n/. When it gets a new pidgin.pot it merges the updates to all translations and bumps the "last updated" timestamp. Because of this it's difficult to tell which translations have updates from translators. Because of this we fetch and commit '''all''' translations from Transifex before releasing. However, some translators have commit access to our repository and commit their translations directly. We need to upload these translations to Transifex before fetching everything.
     16
     17'''Note'''[[br]]
     18Ask Mark Doliner or Richard Laager if you need administrative access to [https://www.transifex.com/projects/p/pidgin/resources/ Pidgin's Transifex project] for the following steps.
     19
     20'''Steps'''
     21 1. Upload [query:?status=new&type=translation&order=priority pending translation updates] from our Trac to [https://www.transifex.com/projects/p/pidgin/resources/ Transifex].
     22 2. Find translations that have been committed directly since the last release and upload these to [https://www.transifex.com/projects/p/pidgin/resources/ Transifex].
     23{{{
     24hg log -b BRANCH_NAME po/
     25}}}
     26 3. Fetch and commit all translations from Transifex.
     27{{{
     28TODO
     29}}}
     30
     31TODO: Need to strip location info or does Transifex do this for us? `XGETTEXT_ARGS=--no-location intltool-update LL`[[br]]
     32TODO: Need to check for mismatched c-format specifiers or does Transifex do this for us? `msgfmt -cv NN`
     33
     34== Other Pre-Release Steps ==
    1435 1. Check there are no open tickets for this release milestone
    1536 1. Make sure the date and version number are correct in !ChangeLog
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!