Add items to release process:

* check all repos are up to date
* check the release notes are OK in all languages

wiki/src/contribute/release_process.mdwn

@@ -1240,6 +1240,13 @@ website:
 
 The release is now public! Woo!
 
+Check translation are correct
+-----------------------------
+
+Once the push is over and the live website is build, check that each
+`news/version_${VERSION}` HTML and RSS pages looks OK in all supported
+languages.
+
 Bug tracker
 -----------
 
@@ -1465,6 +1472,8 @@ this, and skip what does not make sense for a RC.
 1. Push the resulting branches.
 1. Make sure Jenkins manages to build all updated major branches:
    <https://jenkins.tails.boum.org/>.
+1. Make sure you pushed all changes in every of our Git repo (including our
+   Debian packages ones).
 1. Delete the _Release Manager View for ${VERSION_:?}_ Redmine custom query.
 1. Ensure the next two releases have their own _Release Manager View_.
 1. On the [[!tails_roadmap]], update the *Due date* for the *Holes