[Pidgin] ReleaseProcess modified

[Pidgin]

Page "ReleaseProcess" was changed by MarkDoliner
Diff URL: <https://developer.pidgin.im/wiki/ReleaseProcess?action=diff&version=67>
Revision 67
Comment: New steps for getting updated translations.
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: ReleaseProcess
=========================================================================
--- ReleaseProcess (version: 66)
+++ ReleaseProcess (version: 67)
@@ -9,8 +9,29 @@
  1. Make sure the newest pidgin.pot exists at [https://www.transifex.com/projects/p/pidgin/resources/ Transifex]
  1. Send an email to translators at pidgin.im and devel at pidgin.im announcing the string freeze.
 
-= Pre Release =
- 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`"
+= Pre-Release =
+== Commit Updated Translations ==
+'''Background'''[[br]]
+Transifex 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.
+
+'''Note'''[[br]]
+Ask 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.
+
+'''Steps'''
+ 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].
+ 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].
+{{{
+hg log -b BRANCH_NAME po/
+}}}
+ 3. Fetch and commit all translations from Transifex.
+{{{
+TODO
+}}}
+
+TODO: Need to strip location info or does Transifex do this for us? `XGETTEXT_ARGS=--no-location intltool-update LL`[[br]]
+TODO: Need to check for mismatched c-format specifiers or does Transifex do this for us? `msgfmt -cv NN`
+
+== Other Pre-Release Steps ==
  1. Check there are no open tickets for this release milestone
  1. Make sure the date and version number are correct in !ChangeLog
  1. Change version number at the top of configure.ac, set {{{purple_version_suffix}}} '''and''' {{{gnt_version_suffix}}} to {{{[betaN]}}} for betas and {{{[]}}} for a full release
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://developer.pidgin.im/wiki/ReleaseProcess>
Pidgin <https://pidgin.im>
Pidgin

This is an automated message. Someone added your email address to be
notified of changes on 'ReleaseProcess' page.
If it was not you, please report to datallah at pidgin.im.