Sorry for the late pile of strings from the About page. We’re frozen. Expect a release in about 68-72 hours, on Thursday, December 12. Please file a ticket for any typos or issues.
Tagged: string freeze Toggle Comment Threads | Keyboard Shortcuts
Guessing there will be no string freeze at all this time around?
We added four final strings to WordPress 3.7. All of them are used to communicate update failures to users. So while they should never be used, when they are needed, it’s super important for them to be accurate.
Thanks for your understanding! At this point, we’re done with 3.7. Expect a release in the next 18-36 hours.
Hello everyone! Following up on my 3.7 strings post — we are now in a 100% string freeze for WordPress 3.7. I’ve just pushed the final 55 strings for the release. The bulk of these are for A) the about page and B) email notifications for background updates.
I don’t expect for there to be any more string changes. Of course, if you catch a typo, let us know.
We’ll be releasing 3.7 RC1 in a few hours, and if all goes to plan, we’ll be releasing WordPress 3.7 before the middle of next week.
Should we change one more string in 3.6?
https://core.trac.wordpress.org/changeset/24860 changed “Compare two revisions” to “Compare any two revisions”. However, the help text was not updated: https://core.trac.wordpress.org/attachment/ticket/24804/24804.19.diff. Can I get a quick consensus on whether it’s okay to have one final string to translate when you go to package 3.6?
WordPress 3.6 is 100% string frozen.
There are now 11 final strings waiting to be translated on http://translate.wordpress.org/projects/wp/3.6.x/admin. There will be no more string changes for 3.6. Thanks all of you for your patience, especially with the about page. You guys are awesome and we’ll be better with the next release.
We are currently targeting WordPress 3.6 final for tomorrow, July 31, no later than 1600 or 1700 GMT, give or take.
Some of you have noted that the credits page does not reflect all translators, only validators. It will by tomorrow.
String freeze. By now you have probably noticed that WordPress 3.6 RC1 was released a little more than a week ago. This usually corresponds to a string freeze, though there’s been a bit of a drip-drip of some more strings that needed to be translated.
At this point, please consider strings formally frozen. If there are any necessary changes, @markjaquith and I will beg for forgiveness.
Well, we’ll actually start begging for forgiveness in advance. The about page has not been updated for 3.6, and we will be pushing all of those strings in the next 24-36 hours. Once pushed, there will be no changes to them (previously, we’ve tinkered with them a bit); it too will be frozen. The about page is a good amount of strings, but since so many of you are so far along in translating WordPress 3.6 (many of you only have two dozen short strings to go), we’re really confident in your abilities — and, of course, appreciate your hard work in making WordPress available in your language.
Timeline: At this time, I would expect WordPress 3.6 to be released early next week.
BuddyPress 1.7 is now in Release Candidate 1 (read our announcement) and we are now in string freeze for the translations.
We’re still aiming to release WordPress 3.5 tomorrow (target is 16:00 UTC). In the meantime, we’ve made two more string changes in the interest of clarifying some of the gallery settings. Both suggestions came from translators (and others) —
- “Random” (with the context “gallery order”) is now “Random Order”
- “Describe this image…” is now “Caption this image…”
Note there are also “Describe this audio/video/file…” strings, but they can only be triggers by plugins for WordPress 3.5, so I didn’t want to needlessly give you three more strings to translate.
That’s it, by the way. We’ve continued to make a few tweaks but at this point, if it hasn’t been proposed or reported, we’re done.
You guys rock, talk to you tomorrow!
Hello all, there were two (very short) strings added after WordPress 3.5’s string freeze to account for some final changes to the media UI:
- “Add to Gallery”, the title of a screen. There is also “Add to gallery” (a button), which was added previously.
- “Reverse order”, used on a button to flip the sort order of a gallery.
Two more strings already existed, but they moved from the admin to the frontend. If these strings were longer, I would try to manually copy it over from the other project, but it is probably easier if you just re-translate it:
- “No items found.”
- “Set featured image”
I appreciate your understanding.
Our target release date remains Wednesday, December 5, 2012. Zé asked for a prediction as to time. I’m not sure yet, but the window would be between 1600 UTC and 2330 UTC, hopefully toward the earlier side but you never know.
Strings for WordPress 3.5 are now frozen.
The targeted release date remains December 5, 2012 (the same date we announced at the start of the cycle).
Unfortunately, this means I’m very late in formally declaring a string freeze. This is entirely on me and I accept responsibility for the delay.
With the exception of the About page, we’ve had only a handful of string changes over the last week. Most translations seem to be in fantastic shape this release, which is a great sight to see. I hope all of you are able to step up and push through.
If you find any typos or other issues, please report them to http://core.trac.wordpress.org/. If you have any questions (or are just plain frustrated with me), feel free to leave a comment.
A few string changes:
- http://core.trac.wordpress.org/changeset/19571 — “Contributing Developers”, a string that the credits API will be returning. (Reported here on wppolyglots.)
- http://core.trac.wordpress.org/changeset/19569 — We accidentally left in a few references to “Admin Bar” when it should now be “Toolbar”.
Both of these changes came from reports from translators. This is all we’ve had since string freeze, and all we are likely to have, unless one of you notice something else.
As a reminder, we’re moving very swiftly to a final release. It may happen Monday. I will post here as we are running through the release checklist (as in, 15–60 minutes before release). It should be noted that we never release if there was a change to core in the previous 24 hours, so I will try to post here with some additional lead time as well.
We’re in string freeze.
Heads up on timing: We’re aiming to release 3.3 final before December 13.
Please post here and use the “core” tag if there are any issues, typos, etc. If we need to change a string, I will post here (and beg for forgiveness). Tickets with potential string changes will be marked with the ‘i18n-change’ keyword.
WordPress 3.2 has now hit RC1. That means we’re in string freeze.
If there’s something we absolutely need to change, we will, but I’ll be updating you here. Potential string changes will be monitored on Trac using the i18n-change keyword.
Please note, the freeze does *not* apply to Twenty Eleven. We’re not quite done there yet.