Manual Release Packages

To release your translations manually, you need to manually create a release package from your local WordPress site (http://locale.wordpress.org). Locale Managers have access to do that.

Before you package and build your localized version of WordPress, you should make sure everything is ready.

1. Check in all updated files into the current branch directory via 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/. under i18n.svn.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// (Access to SVN may need to be requested via make.wordpress.org/polyglots; it’s handled separately and not automatically connected to the roles “Locale Manager” or “General Translation EditorGeneral Translation Editor A General Translation Editor (often referred to as GTE) is a person, who has global access to validate strings on all projects for a specific locale.”).
2. The 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. consists of four different sub-projects that all need to be translated to 100%: WordPress, Countries & Cities, Administration, and Network Admin. Make sure all the stringsString A string is a translatable part of the software. A translation consists of a multitude of localized strings. are translated.
3. In your SVN directory, copy the current branch directory and create a new tag directory under locale/tags/X.X.X

Got it all ready? Let’s package WordPress!

Packaging Process – Step by step guide

First, you’ll need to obtain the revision number of the corresponding WordPress package. Releases are available in the list of tags on core Trac or on this page in the “Release Revisions” section. This list does not include pre-releases including betas and release candidates. For those, you will need to look for a reference to the version “bump” in the build.trac.wordpress.org revision log.

Once you have the revision number of the version you’ll be packaging, it’s time to build the actual package. To do that, follow these steps:

1. Log in as a General Translation Editor to your local WordPress site (locale.wordpress.org)
2. Go to “Tools → Release Packages”.
3. Scroll down to “Build New Package” section.
4. For “Where should we get your translations from”, select “translate.wordpress.orgtranslate.wordpress.org The platform for contributing to the translation of WordPress core, themes and plugins.” if you want to use those current translations. If you’ve checked in translated message files in svn, select “SubversionSVN 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/.”.
5. For “Locale branch for dist files”, select the location of your translated files under https://i18n.svn.wordpress.org/locale/.
6. For “WordPress Branch”, select the corresponding original branch.
7. For “WordPress revision”, select the revision number you found at the beginning.
8. “WordPress Version” will be used as the package name (e.g. 3.9, 3.9-beta3, 3.9-RC1).
9. Click the “Build Package” button.

Important: Before releasing the package to the public, download the zip or tar.gz file from the links at the top of the page and test it.

Top ↑

Releasing New Versions

After building a new package, you can share the download URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org among your translation team for testing. You can find the URLs under the “Links” column on the Translations for page, in .zip or .tar.gz format.

If testing goes well and you’re ready to release the final version to the public, simply click the version’s “Release” link under the “Action” column. This will mark the official release of that version. Users will be prompted for an upgrade of their language package on their dashboard, and download information on your locale site will be updated.

Top ↑

Release Revisions

View the current list of available tags for each release here and use the number in the “Rev” column as the revision number.

Last updated: August 18, 2020