WordPress 4.3 instruction manual

The upcoming releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. 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 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/, you do not need to do anything. Your release packageRelease package 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.3, please ensure you have an empty branches/4.3/dist or tags/4.3/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 branches/4.3 or tags/4.3 is empty. An example would be nl_NLYour 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 branches/4.3/dist or tags/4.3/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_NOYour 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 coreCore 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 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. 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 RC2 build generated from tags/4.3-RC2 waiting for you on your dashboard. Please inspect these ZIPs. Those localesLocale 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: de_DE_formal, de_DE, it_IT, en_CA, en_AU, eo, nb_NO, sv_SE, tr_TR, nn_NO, ro_RO, nl_NL, ko_KR, eu, hy, and bs_BA (zip links).

Language packs are generated for de_DE_formal, de_DE, el, he_IL, it_IT, id_ID, gl_ES, fr_FR, en_CA, en_AU, eo, ja, nb_NO, sv_SE, es_ES, th, tr_TR, sk_SK, sr_RS, nn_NO, pl_PL, ro_RO, nl_NL, ko_KR, eu, hy, bs_BA, ca, and bg_BG.

Locales which are at 100% but skipped because of missing tags/branches: el, he_IL, id_ID, gl_ES, fr_FR, ja, es_ES, th, sk_SK, sr_RS, pl_PL, ca, and bg_BG.

If you have any questions, comments, concerns, or issues, please comment here or find us in #polyglots on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

#4-3, #announcement