I can’t build 3.7 without revision What is…

I can’t build 3.7 without revision. What is the revision for 3.7 ?

#3-7, #my_mm, #release

FYI from @dd32 ‘s comment on core P2…

FYI – from @dd32 ‘s comment on core P2:

Localised (non-english) installs are currently not receiving Background Updates.

3.7.1 Background updates will be enabled for localised builds shortly, there’s just been some unexpected WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ infrastructure work that needs to happen first.

They’ll be enabled in the near future (next few days for sure) but in the meantime you can either update manually, or, if you’re not being affected by any of the bugs fixed in it (there’s no security fixes in this release) simply wait a few extra days for it to kick in.

Let’s not freak out 🙂 The best thing we can do for the users with localized install is to provide correct information about the situation.

Also from the same thread:

Background updates occur at 7am/7pm Local time (whatever the timezone your blog is set to).

Background updates are being rolled out at a slow pace to all sites, it may be a few hours before your site has been given the autoupdate offering, and then it’ll wait until the next 7am/7pm timeslot before it attempts the update.

You’ll receive an email when the autoupdate completes (or if it encounters an error which prevents it from updating)

#3-7, #update

WordPress 3.7.1 was released Build it off the…

WordPress 3.7.1 was released. Build it off the 3.7.1 tag and you’ll be fine (and won’t need a version number — but it is 25924).

#3-7, #core, #release

function send debug email is not i18n’d in…

function send_debug_email() is not i18nInternationalization Internationalization (sometimes shortened to I18N , meaning “I - eighteen letters -N”) is the process of planning and implementing products and services so that they can easily be adapted to specific local languages and cultures, a process called localization. This is the process of making software translatable. Information about Internationalization for developers can be found in the Developer’s handbooks.’d (in class-wp-upgrader.php, bottom method). Should’nt it be? It makes for mixed English-French update debug messages for certain users here…

#3-7

We added four final strings to WordPress 3.7…

We added four final stringsString A string is a translatable part of the software. A translation consists of a multitude of localized 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.

#3-7, #string-change, #string-freeze

Hi @Ze and @nacin I can´t create a…

Hi @Ze and @nacin,

I can´t create a RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. Build in RosettaRosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. for de_DE to test it.

My workflow:

1. add all dependent files into svn at /tags/3.7/dist (liesmich.htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. & wp-config.php)
2. commit changes to svn
3. go to rosetta

Build a new packet:

  • source: translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.
  • LocaleLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/ branch: /tags/3.7
  • Project: Development trunk
  • Revision: 25851
  • Version: 3.7-RC1-25851
  • push the button

I get following error message:

Fehler beim Kopieren von /tmp/rosettaVtIemt/de_DE/dist/liesmich.html zu /tmp/rosetta4vXl9F/wordpress!

What can I do to fix this problem?

Best regards,
Birgit

#3-7, #build, #de_de, #request, #rosetta

Testing the Japanese version on my local machine…

Testing the Japanese version on my local machine and the automatic update from Beta2 to RC1 works fine except:

1. $wp_local_package in wp-includes/version.php is removed after the update.
2. Translations is not updated.

Step to reproduce:
1. Install WordPress 3.7 betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 2 Japanese version on your local machine.
2. After a while it is automatically updated to RC1.
3. Look into wp-includes/version.php, you will find wp_local_package is gone.
4. Look into wp-content/languages/ja.po and you will find “PO-Revision-Date: 2013-10-11 19:25:37+0000\n”, though the ja.po file of RC1 says “PO-Revision-Date: 2013-10-18 13:03:34+0000\n”

Does it happen because the all files are still in trunk?

#3-7

Hello everyone Following up on my 3.7 strings…

Hello everyone! Following up on my 3.7 strings post — we are now in a 100% string freezeString freeze The term "string freeze" is used by the core team to mark the end of changes to the strings of an upcoming release. A string freeze also means that there will be no more strings added to the core project. Sometimes a string freeze has two phases a soft freeze and a hard freeze. A string freeze is announced on the Polyglots blog by the current release lead. for WordPress 3.7. I’ve just pushed the final 55 stringsString A string is a translatable part of the software. A translation consists of a multitude of localized 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 stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. 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.

#3-7, #core, #string-freeze

Strings for WordPress 3.7 Hello all I want…

StringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. for WordPress 3.7

Hello, all. I want to explain what was going on with 3.7. After we rearranged our code repositories for WordPress core, our tools that generate and import strings needed to be adjusted. At the time I also knew that a 3.6.1 security release was being prepared, so we moved the “Development” project to “3.6.x” to make sure all 3.6 and 3.6.1 releases went smoothly.

GlotPressGlotPress GlotPress is the translation management software that powers Translate.WordPress.org. More information is available at glotpress.org. is not yet good at “branching,” so after I move “3.6.x” back to “Development” and create an empty “3.6.x”, I have a script that handles exporting and importing all translations. Once that happens, I can then update the original strings in the “Development” branch to reflect 3.7. If I were to just create an empty “3.6.x” and let you do the export from “Development” and import into “3.6.x”, your exports will be incomplete because the originals changed, and that’s no fun, and it makes it much harder for you to release security releases.

(Note: This isn’t a complaint about GlotPress. I’ve had conversations with @markoheijnen about how a few adjustments can make GlotPress better for us, and I’m excited.)

I cited 3.7 repositoryWordPress Localization Repository The WordPress Localization Repository at https://i18n.svn.wordpress.org/ is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details. changes as the catalyst, but we’ve actually done this shuffling previously. No one noticed until now because this release cycle is so short. But, I’ll argue that this “shuffle” is actually a good thing. Otherwise, what happens is a few strings change per week during early “alpha” development, and translators jump all over those. But in reality, those strings are still in flux, which means you’re just doing extra work because GlotPress presented you with a stringString A string is a translatable part of the software. A translation consists of a multitude of localized strings. that we might change in a few days. That’s no fun for anyone, and it makes me feel really bad, because your time is valuable. Waiting a few weeks before we start to populate strings into “Development” is actually ideal.

Okay, what about string freezeString freeze The term "string freeze" is used by the core team to mark the end of changes to the strings of an upcoming release. A string freeze also means that there will be no more strings added to the core project. Sometimes a string freeze has two phases a soft freeze and a hard freeze. A string freeze is announced on the Polyglots blog by the current release lead.?

You may have also noticed that 3.7 was a very “low-level” release. It primarily focused on bug fixes, code improvements, and updates. There were no major user-facing features or UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. changes, which also meant there were very few strings. there are only around 76 strings new in 3.7. I imported the new strings less than two hours ago, and then I went through each of them to confirm there were no typos or changes to make. The crazy thing is in two hours, two translators are already almost done! (Props @damst and @SteveAgl.) That just goes to show how easy and quick it will be to update your translations for WordPress 3.7.

It also showed how quickly new strings are translated. As I said, I want to make sure you feel your time is valued. So: let’s consider this point to be a “string freeze” with a qualifier. The 76 strings have been double-checked and are ready to go, and you should start translating them today. The qualifier: There will be some new strings that get added over the next week. First, we’re still polishing a few things. Second, there is also the about page, which I promise you’ll have a week to translate. We’re planning to launch 3.7 the week of October 14, so expect to hear more next week.

What about language packs?

The general concept of “language packs” are new in 3.7. But, a lot of the processes for how WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ will be handling those is still not settled (more to come here). However, If you’re looking for something to do, may I suggest you make sure your translations for the WordPress importer plugins are up to date? Upon 3.7’s launch, any 100% translations for these plugins will be delivered to WordPress sites during updates. The same goes for bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org., BuddyPress, and default themes, too.

While after reading this you may come to your own conclusion, I promise there was no conspiracy, negligence, or incompetence to keep you all from translating 3.7. 🙂

Finally: If you’re at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe this weekend, please come find me to chat! I want to hear your thoughts and ideas.

Happy translating!

#3-7, #announcement, #core

Heads up all Trunk is upp to date…

Heads up all. Trunk is upp to date again.

#3-7, #project, #trunk