The upcoming release of WordPress will become available in the next 24 hours. This is a reminder on what you should do to benefit of the automated package build process.
- If you have never had any custom changes and i18n.svn.wordpress.org is entirely empty for your locale 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/, you do not need to do anything. Your release package A release package is a packaged version of WordPress. That is, a ZIP file consisting of WordPress in its entirety, along with PO and MO files for core, the PO and MO files of default themes and Akismet, and any custom changes a locale has. In the past, most locales built their release package using the form in Rosetta’s dashboard. will be created automatically for you. An example locale is en_GB.
- If you have no custom changes for 4.2, please ensure you have an empty
tags/4.2/dist directory at i18n.svn.wordpress.org. (Having an empty
trunk/dist directory does not help you.) You do not need a
dist directory if
tags/4.2 is empty. An example would be nl_NL. Your release package will be created automatically for you.
- If you have minor custom changes consisting of, at most, a translated readme, license file, and wp-config-sample.php, please ensure these files exist in a
tags/4.2/dist directory at i18n.svn.wordpress.org. (Having your stuff in only
trunk/dist does not count.) An example would be de_DE or nn_NO. Your release package will be created automatically for you.
- If you have extensive custom changes consisting of other files, such as
wp-content/languages/$locale.php or core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. modifications, you will need to create a package via Rosetta 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. as you have done in the past.
If your locale is currently eligible for automatic creation of release packages (which includes being at 100%), you’ll find an RC4 build generated from tags/4.2-RC4 waiting for you on your dashboard. Please inspect these ZIPs. Those locales 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/ are: nn_NO, eo, en_GB, nl_NL, en_CA, de_DE, is_IS, it_IT, de_CH, el, nb_NO, sv_SE, da_DK, en_AU, bs_BA, tr_TR, th, ro_RO, eu, and lt_LT (zip links).
Language packs are generated for bg_BG, bs_BA, ca, cy, da_DK, de_CH, de_DE, el, en_AU, en_CA, en_GB, eo, es_ES, eu, fi, fr_FR, gl_ES, he_IL, hu_HU, id_ID, is_IS, it_IT, ja, lt_LT, nb_NO, nl_NL, nn_NO, pt_BR, ro_RO, ru_RU, sk_SK, sq, sr_RS, sv_SE, th, tr_TR, and uk.
Locales which are at 100% but skipped because of missing tags/branches: bg_BG, ca, cy, es_ES, fi, fr_FR, gl_ES, he_IL, hu_HU, id_ID, ja, pt_BR, ru_RU, sk_SK, sq, sr_RS, and uk.
Skipped Locales which are not at 100% but at least 90%: af (90%), ar (99%), az (98%), bel (99%), bn_BD (99%), cs_CZ (98%), es_CL (90%), es_MX (96%), es_PE (96%), et (94%), fa_IR (99%), fr_BE (99%), haz (99%), hr (96%), km (94%), ko_KR (96%), lv (96%), mk_MK (99%), ms_MY (92%), my_MM (96%), ps (96%), pt_PT (99%), rhg (98%), si_LK (97%), sl_SI (99%), tl (98%), ug_CN (96%), uz_UZ (95%), vi (99%), zh_CN (96%) and zh_TW (96%).
If you have any questions, comments, concerns, or issues, please comment here or find me in #polyglots on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..