We don't need the release manager's view here.

1 files changed, 0 insertions, 56 deletions

diff --git a/customising/translation.md b/customising/translation.md
index a403f6396..4f3c39270 100644
--- a/customising/translation.md
+++ b/customising/translation.md
@@ -121,59 +121,3 @@ is cut. During such time, you must not introduce new strings to the code if
 your work is due for inclusion in this release. This is necessary to allow
 translators time to complete and check their translations against all the known
 strings.
-
-## Translation process: release manager's view
-
-**If you're responsible for coordinating translators and developers so that all
-the work comes together in a new release, you're the release manager.**
-
-This is the most complicated of the three roles -- the chances are this doesn't
-apply to you, so only read it if you want to understand how the process works.
-
-As the release manager, before you cut a new release branch, you must do the
-following:
-
-### Before the release candidate date:
-
-* Pick a date for the release branch to be cut ("release candidate date").
-* Make an announcement to the translators (using the "announcements"
-  feature in Transifex) that they should ensure they have any pending
-  translations saved in Transifex before the release candidate date.
-* Make an announcement to the developers that all new strings should
-  be committed before the release candidate date.
-
-### On the release candidate date:
-
-* Download all the current translations with `tx pull -a -f` and commit  (important: there's no revision history in Transifex!).
-* You should also commit these translations to a hotfix for the
-  previous version, so they are preserved against the last known
-  good msgids.
-* Regenerate the POT file and individual PO files for each language,
-  using `bundle exec rake gettext:store_model_attributes`, followed by 
-  `bundle exec rake gettext:find`
-  * Be careful not to include msgids from themes in `lib/themes`;
-    you might want to move them out of the way before running
-    the above commands.
-  * This updates the PO template, but also merges it with the
-    individual PO files, marking strings that have only changed
-    slightly as "fuzzy".
-* Re-upload the POT and PO files to Transifex from the
-  current release branch with `tx push -s -t`
-  * The point of uploading the PO files is that Transifex
-    converts the "fuzzy" suggestions from Transifex into
-    "suggestions" under each source string.
-  * Note that Transifex *does not* preserve fuzzy strings in the
-    PO files it makes available for download, on the grounds
-    that Transifex supports multiple suggestions, whereas
-    gettext only allows one fuzzy suggestion per msgid.
-* Remove the fuzzy strings from the local PO files (because they
-  make Rails very noisy), and then commit the result. You can do
-  this by re-pulling from Transifex.
-
-### On the release date:
-
-* Download and commit all the current translations to the current release branch.
-
-
-
-