1. Please make the new version announcement post content (HTML) available for translation before launch.
2. Please change the list of changes link in the WP admin -> Updates section to the announcement post.
3. Try to make the announcement post link redirect to a local Rosetta translation of it if available.
Main idea: With incoming WP versions, it would be great if we could also have the announcement post content (HTML) available for translation, so that when a new version launches, we just push the Publish button. Thanks to that, whenever a new version comes, there’s already an announcement post in local languages ready for people to see.
An idea for automation in the future: It would be even better if the local Rosetta sites would have a dropdown menu and Translation Editors could choose, which English wordpress.org blog post is the current post a translation of (like in WPML), even if its status is set to Draft. Then, publishing the main English post would also publish all connected posts which have a status of “Auto-publish with original post” (a new status would have to be created).
2nd thing: in the WP admin panel, there’s a notification with each new version available. Under the Update section, there’s a link to the English wordpress.org site for a list of changes. That post is technically translatable (example: https://codex.wordpress.org/Version_4.2.4 ), but the languages menu isn’t clearly visible and people are likely to leave when they see English instead of their local language. Another issue is that this is a highly technical post, not user-friendly like the announcement posts. We should change this link to the announcement post, would be great if it could even be a localized version from Rosetta sites.
For this to work with Rosetta sites, we would have to have a small script which could check a database for local translations of the announcement post, and – if they exist – redirect accordingly. A simple implementation would require Translation Editors to add the URL manually, while a more automated solution would have to implement the dropdown translation menu, which is described above.
Maybe there’s an easier way to get all these things to work. Open for discussion.