The last strings for 4.7 (the about page strings) have been imported to the development project and that means no strings will change anymore before Tuesday, December 6th, the expected release date for WordPress 4.7.
That means there are two things for all GTEs to do now:
1. Translate the 4.7 project, Admin and Network admin
If all you have is a license, readme, and wp-config-sample.php (or no custom changes at all), everything will be automated for you if you follow the instructions above. Both language packs and release packages will automatically be created. If you are not at 100% at that time, then language packs and release packages will be created when you reach 100%. If you later modify a translation (to fix a typo, for example), your language pack and release package will be regenerated.
If you have extensive custom changes,you will need to manually create a package via Rosetta as you have done in the past.
WordPress 4.7 RC1 was announced on Friday and with it, all the strings in this release with the exception of the About page strings are now effectively frozen. A soft string freeze means they won’t be changed and no new ones will be added before the release in the first week of December.
Translate the 4.7 project, Admin, Network admin, Continent & cities and Twenty Seventeen
If your Development project is not translated to 100%, this is a good time to take care of that. Head to translate.wordpress.org and translate:
According to the development schedule, hard strings freeze should come on November 29th (+1d) and the release is expected on December 6th (+1d). There will be another post here and a global ping when that happens.
Please add me as editor of the Chinese (Taiwan) translation plug for https://translate.wordpress.org/projects/wp-plugins/hueman-addons at the request Hueman addons plug.
Chinese (Taiwan) (#zh_TW) (@kaiconan)
There may not be all 5 translation files for your locale. That’s because some of the plugins are 100% completed already.
Preparing these files involved a bit of manual work on my side, so if you see any technical flaws it’s probably my fault. Please don’t hesitate to point them out, and I’d be glad to fix/investigate the cause.
A team o2 can be used for whatever your local community needs. For example, you can use it to talk about WordCamps, meetups, translations, support, documentation, meeting summaries, discussions about new ideas and the likes – in your language.
It can be a great platform for new people who would like to join your translation team. Or a great place to post about upcoming events and invite people to suggest topics. Basically, it’s an open wall for your community to discuss local issues. An official one, on your official local WordPress.org site.
How does your team get an o2?
Every Rosetta site should have one and every team can get one. If your locale is currently released for 4.6, your o2 is already created. You can check if you have one by adding “/team” to the address of your Rosetta site. If you don’t already have one, please feel free to request one in a comment below this post.
All locale managers get an Editor level access to the new o2s which allows them to customize the site and moderate content. o2s are separate WordPress installs from your Rosetta site, but all your current Locale Managers and Editors are added as users by default. All WordPress.org users can post and comment on locale o2s.
We’re delighted to finally be able to add this feature for all teams and we hope you find it useful to get new contributors and make communication about contributing to WordPress easier in your language.