WordPress 4.9 should be released today – prepare your locales

WordPress 4.9 should be released today – prepare your locales

Dear Polyglots,

The last strings for 4.9 have been frozen since November 9th and WordPress 4.9 is about to be released.

That means there are two things for all GTEs to do now:

1. Translate the 4.9 project, Admin and Network admin

It’s time to head to translate.wordpress.org and finish translating the last batch of new strings.

Please don’t forget that in order to qualify for an automatic release, you need to have all strings in the following projects translated 100%:

2. Prepare the SVN directory for your locale for automated packages

Handbook page for reference: Automated release packages

Does my locale qualify for automated release?

  • 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.

On Slack, watch out for messages like this one:

translation-bot

Your locale is good to go if you see your locale in the “x release packages for y were built” message.


This is also a global ping for GTEs for locales that are currently at more than 50% and less than 100%.

26 locales are already at 100% – thank you!

Dev between 95% and 100% (15)

Dev between 90% and 95% (14)

Dev between 50% and 90% (51)

The release is due today and this is a very short notice, a last minute string was added yesterday as well so thank you in advance to everyone who makes time to get their locale to 100%. For those who don’t the next couple of weeks are a great time to get this done as well so no stress and happy translating!

Petya

#announcement

#hard-freeze, #wordpress-4-9

WCUS Contributor Day Leads Needed

Hey all, I’m organizing the WordCamp US contributor day. I need someone, or better yet a couple people, who will be attending and able to lead the polyglots group during contributor day. Most of the responsibility if helping facilitate the group on the day of, but there is also some planning to do ahead of time.

What I need from the lead(s):
1) What do you want/need to make it an effective day for your group? (to be near other teams, do you need any particular setup, etc)
2) What will the plan be for new contributors in your group?
3) What will the plan be for existing contributors?

#2 and 3 aren’t needed right now, but I want to make sure that all groups have a plan in place for both new and existing contributors to make the day as productive as possible.

#request

We’re in hard string freeze for 4.7 – Prepare your locales for the the release

Dear Polyglots,

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

It’s time to head to translate.wordpress.org and finish translating the last batch of new strings.

Please don’t forget that in order to qualify for an automatic release, you need to have all strings in the following projects translated 100%:

There is also a new default theme that comes with 4.7 – Twenty Seventeen which can also use some of your time.

2. Prepare the SVN directory for your locale for automated packages

Handbook page for reference: Automated release packages

Does my locale qualify for automated release?

  • 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.

On Slack, watch out for messages like this one:

translation-bot

Your locale is good to go if you see your locale in the “x release packages for y were built” message.


This is also a global ping for GTEs for locales that are currently at more than 50% and less than 100%.

4 locales are already at 100% – thank you!

Dev between 95% and 100% (15)

Dev between 90% and 95% (14)

Dev between 50% and 90% (51)

The release is due on Tuesday, which makes this a little bit of a short notice so thank you in advance to everyone who makes time to get their locale to 100%.

Happy translating <3

Petya

#announcement

#hard-freeze, #wordpress-4-7

WordPress 4.7 is in soft string freeze

Hello everyone,

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:

20 locales are already at 100%, very well done! Here’s a ping for the GTEs of locales that are at more than 50% right now.

Dev between 95% and 100% (15)

Dev between 90% and 95% (14)

Dev between 50% and 90% (51)

Upcoming hard string freeze

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.

Thank you all for your hard work!

#soft-string-freeze, #wordpress-4-7

Hi Polyglots, I am the…

Hi Polyglots, I am the plugin author for Genesis Translations. Please add the following WordPress.org user as PTE for their respective locales:

#editor-requests

Help us validate 5 WooCommerce extensions in 24 locales

Thanks to GoDaddy’s initiative to support localization of WordPress plugins & themes, we at Automattic received translations of 5 plugins in 24 locales.

  1. WooCommerce
  2. Storefront Product Pagination
  3. Storefront Product Sharing
  4. Storefront Sticky Add to Cart
  5. WooCommerce Gateway Stripe

Validation process (2 options)

There are two ways you can use the translation files we have.

1. Review the translation using the PO files, then import them (you will receive credits).

OR

2. Review Waiting strings on translate.wordpress.org. I will import everything in one week (in case GTEs prefer the method 1) as Waiting status.

  • Please feel free to leave a comment if you want the import to happen sooner for your locale.
  • If you don’t have time to validate, the translations will just stay as “Waiting”. There is no time limit to review them.

Locales

Note to validators

  • 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.
  • Thanks in advance for your help!

We’re in hard string freeze for 4.6 – Prepare your locales for the the release

Dear Polyglots,

A little while back the WordPress 4.6 hard string freeze was announced and that means no strings will change anymore before August 16th, when WordPress 4.6 will be released.

That means there are two things for all GTEs to do now:

1. Translate the 4.6 project, Admin, Network admin and Continent & cities

The release will hit on Tuesday, August 16th. It’s time to head to translate.wordpress.org and finish translating the last batch of new strings.

Please don’t forget that in order to qualify for an automatic release, you need to have all strings in the following projects translated 100%:

2. Prepare the SVN directory for your locale for automated packages

Handbook page for reference: Automated release packages

Does my locale qualify for automated release?

  • 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 are 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.

On Slack, watch out for messages like this one:

translation-bot

Your locale is good to go if you see your locale in the “x release packages for y were built” message.


 

This is a global ping for all General Translation Editors whose locales are more than 50% and less than 100% translated:

18 locales are already at 100%, well done and thank you!

Dev between 95% and 100% (35)

Dev between 90% and 95% (15)

Dev between 50% and 90% (29)

Thank you to everyone who’s already helping bring WordPress to more than 100 languages worldwide.

We’re not allowed to be biased but this release is really special because we’ve got this guy leading it. Let’s make him proud and break a new record releasing on Tuesday, Aug 16th, with 60+ locales. I know we can do it.

Happy translating ❤️

Petya

#announcement