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

Notice of Password Deactivation

Hello everyone, some of you will have the following email in your inbox:

[WordPress.org] Notice of Password Deactivation

Your password on WordPress.org has been deactivated, and you need to reset it to log in again.

We discovered internally a bug in the API used by our open source translation software, GlotPress, that could have potentially exposed user data, including email address and encrypted/hashed password string.

Based on our analysis of the logs, we don’t think this happened, but out of an abundance of caution we’re proactively disabling the passwords on a couple hundred translation volunteer accounts, one of which is yours.

We apologize for this. When you reset your password, please choose a new one, and as always we discourage using the same password across multiple services.
To reset your password please follow the ‘Lost password?’ link on the login page.

Username: ###USERNAME###
Email: ###EMAIL###

Again, we apologize for this. If you have any questions don’t hesitate to post them in the comments or contact me @ocean90 on Slack.

#announcement

Strings for WordPress 4.7 are available for translation

WordPress 4.7 Beta 1 was released a few days ago and now you can start translating WordPress 4.7 on translate.wordpress.org!

WordPress 4.7 Beta 1

The strings are in the Development project at https://translate.wordpress.org/projects/wp/dev. The strings of WordPress 4.6 have been moved to https://translate.wordpress.org/projects/wp/4.6.x.

Stats:

  • wp/dev: 415 new strings added, 1477 updated, 29 fuzzied, and 30 obsoleted.
  • wp/dev/admin: 27 new strings added, 1116 updated, 54 fuzzied, and 29 obsoleted.
  • wp/dev/admin/network: 6 new strings added, 273 updated, 8 fuzzied, and 2 obsoleted.

WordPress 4.7 will also introduce a new default theme, Twenty Seventeen. You’ll find its strings at https://translate.wordpress.org/projects/wp-themes/twentyseventeen.

There are a few fuzzy strings which are a good starting point for WordPress 4.7.

WordPress 4.7 is planned for December 6th.

Happy Translating!

#4-7 #announcement

New Team o2s

Two weeks ago we’ve rolled out 11 team o2s for testing. Today we’re pleased to announce that all 71 locales with a current release now have a team o2.

What should you use the o2 for?

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.

The following 60 62 sites were created:

team-site

  • #ary: https://ary.wordpress.org/team/
  • #az: https://az.wordpress.org/team/
  • #bn_BD: https://bn.wordpress.org/team/
  • #bo: https://bo.wordpress.org/team/
  • #ca: https://ca.wordpress.org/team/
  • #cs_CZ: https://cs.wordpress.org/team/
  • #cy: https://cy.wordpress.org/team/
  • #da_DK: https://da.wordpress.org/team/
  • #de_CH: https://de-ch.wordpress.org/team/
  • #el: https://el.wordpress.org/team/
  • #en_AU: https://en-au.wordpress.org/team/
  • #en_CA: https://en-ca.wordpress.org/team/
  • #en_GB: https://en-gb.wordpress.org/team/
  • #en_NZ: https://en-nz.wordpress.org/team/
  • #en_ZA: https://en-za.wordpress.org/team/
  • #eo: https://eo.wordpress.org/team/
  • #es_AR: https://es-ar.wordpress.org/team/
  • #es_CL: https://cl.wordpress.org/team/
  • #es_GT: https://es-gt.wordpress.org/team/
  • #es_MX: https://es-mx.wordpress.org/team/
  • #es_PE: https://pe.wordpress.org/team/
  • #es_VE: https://ve.wordpress.org/team/
  • #eu: https://eu.wordpress.org/team/
  • #fa_IR: https://fa.wordpress.org/team/
  • #fi: https://fi.wordpress.org/team/
  • #fr_BE: https://fr-be.wordpress.org/team/
  • #fr_CA: https://fr-ca.wordpress.org/team/
  • #gd: https://gd.wordpress.org/team/
  • #gl_ES: https://gl.wordpress.org/team/
  • #gu: https://gu.wordpress.org/team/
  • #hau: https://hau.wordpress.org/team/
  • #hi_IN: https://hi.wordpress.org/team/
  • #hr: https://hr.wordpress.org/team/
  • #hu_HU: https://hu.wordpress.org/team/
  • #hy: https://hy.wordpress.org/team/
  • #id_ID: https://id.wordpress.org/team/
  • #is_IS: https://is.wordpress.org/team/
  • #ka_GE: https://ka.wordpress.org/team/
  • #km: https://km.wordpress.org/team/
  • #ko_KR: https://ko.wordpress.org/team/
  • #lt_LT: https://lt.wordpress.org/team/
  • #lv: https://lv.wordpress.org/team/
  • #mr: https://mr.wordpress.org/team/
  • #ms_MY: https://ms.wordpress.org/team/
  • #nb_NO: https://nb.wordpress.org/team/
  • #nn_NO: https://nn.wordpress.org/team/
  • #oci: https://oci.wordpress.org/team/
  • #pl_PL: https://pl.wordpress.org/team/
  • #pt_PT: https://pt.wordpress.org/team/
  • #ro_RO: https://ro.wordpress.org/team/
  • #sk_SK: https://sk.wordpress.org/team/
  • #sl_SI: https://sl.wordpress.org/team/
  • #sq: https://sq.wordpress.org/team/
  • #sr_RS: https://sr.wordpress.org/team/
  • #sv_SE: https://sv.wordpress.org/team/
  • #szl: https://szl.wordpress.org/team/
  • #te: https://te.wordpress.org/team/
  • #th: https://th.wordpress.org/team/
  • #tr_TR: https://tr.wordpress.org/team/
  • #uk: https://uk.wordpress.org/team/
  • #vi: https://vi.wordpress.org/team/
  • #zh_TW: https://tw.wordpress.org/team/

How does o2 work?

A new handbook page “Team o2” has been added to provide some details about the new site, how to manage and use it. Read it and ask any questions that remain in the comments here.

Who has access to the new o2s?

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.

#announcement, #dev-update

Asia Pacific meeting on Wednesdays

Starting this week, we are reviving the Asia Pacific weekly Polyglots meeting.

As mentioned in the polyglots chat last week, this will be an alternative opportunity for those who can’t attend the current meeting because of the timing.

When:
Wednesday at 6am UTC (Wednesday 6:00 UTC)

What:

  • Weekly polyglots meeting with more Asia-Pacific friendly time slot
  • Regular meeting topics plus announcements & discussion specific to the Asia-Pacific region

Who:

Anyone is welcome to attend!

I’m pinging GTEs of Asia & Pacific locales, in case you are not closely following this P2.

Please let me know if you are pinged even though your locale is not in the area (sorry!). And if anyone sees missing locales, please leave a comment as well 🙂

#announcement

Translations for plugins and themes can now be imported with status waiting

I want to inform you about some recent changes to translate.wordpress.org. 👀

See who approved/rejected your translation

It took a while but you can now finally see which user approved (or rejected) a translation. You’ll find the information in the meta sidebar of a translation:

Approved by

Approved by

Rejected by

Rejected by

 

Import with status waiting

This was originally proposed by @akirk in #1654. This feature landed in GlotPress 2.1 but wasn’t available on translate.wordpress.org until now. Since today everyone can import translations with status waiting.

GTEs/PTEs can choose the status when importing a file. The import UI looks like this:

import-status-both

A regular translators can’t choose the status. It’s set to waiting by defaut:

import-status-waiting

Regular translators can use the import functionality only for theme and plugin projects.

This is currently in a testing phase so any feedback is highly appreciated.

 

Other updates:

  • Support added for the Latin version of Hausa
  • Updated locale information for Kyrgyz
  • The native name for Tibetan is renamed to བོད་ཡིག
  • The “Project-Id-Version” for new PO files contains the full project name
  • Imported translations are now also checked for warnings
  • Translations which contain the placeholder for tab characters are automatically fixed

 

Let us know in the comments if you have any questions or found a bug in one of the recent changes. 🐛

#announcement, #dev-update

Faster deployment of language packs for themes and plugins

Since last Friday language packs for themes and plugins are no longer generated every 6-12 hours. Language packs are now build 30 minutes after a change to a translation or an import for new translations has happened.

This means that when you update a theme or a plugin in the future it’s likely that WordPress will also download an up to date language pack. Or, ever had a critical typo in a translation? Just fix it and watch how fast your users will get the updated translation. 🚀

Because we all ❤️ Slack: Each build process is logged in the #meta-language-packs channel:

language-packs-slack-log-png

 

Expect similar changes to language packs for WordPress core soon.

P.S.: As always, all new code is open-sourced. You’ll find it in the meta SVN repository here, here and here.

#announcement, #dev-update

WordPress 4.6.1 has been released It is a…

WordPress 4.6.1 has been released. It is a security and maintenance release and there are no string changes.

In order to benefit from the automated release process make sure that your locale is prepared.

Also released: 4.5.4, 4.4.5, 4.3.6, 4.2.10, 4.1.13, 4.0.13, 3.9.14, 3.8.16, and 3.7.16.

#announcement, #release

WordPress 4.6 has been released

WordPress 4.6 “Pepper”

Thanks to all translators for making WordPress 4.6 available in more than 50 languages! 🙌

#announcement

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

Strings for WordPress 4.6 are now frozen

Hello everyone,

as announced in the release post for the second release candidate of WordPress 4.6, all strings are now frozen, including the about page.

WordPress 4.6 RC2

You’ll find the strings in the admin project: https://translate.wordpress.org/projects/wp/dev/admin

WordPress 4.6 will be released next week on Tuesday, August 16th.

Happy Translating and thanks for your work!

 

P.S.: Don’t forget the subtitles for the release video. 📹

#announcement

Hello Polyglots you can start translating WordPress 4.6…

Hello Polyglots, you can start translating WordPress 4.6!

The strings are in the Development project at https://translate.wordpress.org/projects/wp/dev. The strings for WordPress 4.5 have been moved to https://translate.wordpress.org/projects/wp/4.5.x.

Stats:

  • wp/dev : 44 new strings added, 1276 updated, 21 fuzzied, and 21 obsoleted.
  • wp/dev/admin : 79 new strings added, 943 updated, 37 fuzzied, and 76 obsoleted.
  • wp/dev/admin/network : 10 new strings added, 128 updated, 3 fuzzied, and 9 obsoleted.
  • wp/dev/cc : 32 new strings added, 460 updated, 0 fuzzied, and 0 obsoleted.

There are a few fuzzy strings which are a good starting point for WordPress 4.6.

WordPress 4.6 is planned for August 16th. Happy Translating!

#4-6, #announcement

WordPress 4.5.2 has been released It is a…

WordPress 4.5.2 has been released. It is a security release and there are no string changes.

In order to benefit from the automated release process make sure that your locale is prepared.

Also released: 3.7.14, 3.8.14, 3.9.12, 4.0.11, 4.1.11, 4.2.8, 4.3.4, 4.4.3.

#4-5, #announcement, #release

WordPress 4.5.1 has been released It is a…

WordPress 4.5.1 has been released. It is a maintenance release and there are no string changes.

In order to benefit from the automated release process make sure that your locale is prepared.

#4-5, #announcement, #release

Hello Polyglots you can start translating WordPress 4.5…

Hello Polyglots, you can start translating WordPress 4.5!

The strings are in the Development project at https://translate.wordpress.org/projects/wp/dev. The strings for WordPress 4.4 have been moved to https://translate.wordpress.org/projects/wp/4.4.x. Please note that there are a few fuzzy strings which might be a good starting point for WordPress 4.5.

WordPress 4.5 is planned for April 2016. Happy Translating!

#4-5, #announcement