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 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. 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.
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.
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.
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.
Frequently Asked Questions
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.
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%.
