Commit 40fb44f0 authored by intrigeri's avatar intrigeri
Browse files

Release process: forget about translations done via Git

This does not happen in practice anymore, since our translation platform is up.
parent b178c02b
......@@ -1529,15 +1529,6 @@ section, and publish them on the `$WEBSITE_RELEASE_BRANCH` branch:
git commit -m "Releasing version ${VERSION:?}" && \
git push origin "${WEBSITE_RELEASE_BRANCH:?}"
Then, if you are preparing a final release, email
<>, pointing them to:
- the PO files for the release notes
… so that these pages get translated shortly, perhaps even soon
enough to merge the translations before you publish the release.
Draft the Tor blog post
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment