Automated Release Packages

Please make sure 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/ is always eligible for automated release packagesAutomated Release Packages Automated release packages are release packages of locales that have no custom changes..

A 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. is a ZIP file consisting of WordPress in its entirety, along with translation files for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., the default themes and Akismet, and any custom changes you may have.

Requirements

There are some requirements you have to follow to ensure your locale is eligible for automated release packages.

Top ↑

Never had any custom changes

If you have never had any custom changes and i18n.svn.wordpress.org is entirely empty for your locale or doesn’t exist, you do not need to do anything. Your release package will be created automatically for you. An example locale is en_GB.

Top ↑

No custom changes for the current stable version

If you have no custom changes for the current stable version (like 5.4), please ensure you have an empty branches/5.4 directory at i18n.svn.wordpress.org. Your release package will be created automatically for you.

It’s now recommend to keep the tags/ directory empty and only use branches/, see Repository File Structure.

Top ↑

Minor custom changes for the current stable version

If you have minor custom changes for the current stable version (like 5.4), consisting of, at most, a translated readme, license file, and wp-config-sample.php, please ensure these files exist in a branches/5.4/dist directory at i18n.svn.wordpress.org. 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 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..

For this, we are phasing out the ability to ship any customizations beyond license, readme, and wp-config-sample.php. This means you need to reach out to the WordPress core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. to fold your modifications into the WordPress core. You can start this process by creating a Trac ticket.

Top ↑

Frequently Asked Questions

Top ↑

Is my locale eligible for automated release packages?

Please scroll up to the Requirements section or:

If you go to the releases screen on your Rosetta dashboard (Tools → Release Packages), you’ll see a notice that explains what the system thinks your status is.

Top ↑

When are the packages built?

Release packages and language packs for stable versions are usually built every hour on the hour after the “Development” sub project is at least 90% AND the “Administration” sub project is at least 75%.

Top ↑

How can I trigger a new automated build for my locale?

A new build will be created only if a translation was changed after the latest build. Rejecting and approving one translation within the WordPress project on translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins. is all that is needed.

Top ↑

I didn’t prepare my SVN repo for a new release in time. Help?

No worries. First, create your SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. branches. Since a language pack was probably already built, you have to update one translation (see the question above). Your package will be created during the next build window (see above).

Top ↑

Is there a way to avoid creating new tags/branches which are empty?

Yes. All you have to do is to clear the directory of your locale. With a commit like [i18n-24837] the directory of your locale should only have these empty directories:

.
├── branches
├── tags
└── trunk
    └── dist

The history doesn’t get lost. Your can continue browsing the old files though the revision log.

Last updated: