Automated Release Packages

release package is what you’re used to building using the form on Rosetta’s dashboard. This 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 you have.

Is my locale eligible for automated release packages? Is my locale eligible for automated release packages?

Do you have custom changes? For the purposes of this exercise, your locale falls under one of these four groups:

  • You have never had any custom changes and i18n.svn.wordpress.org is entirely empty for your locale.
  • You have no custom changes for the current stable version.
  • You have minor custom changes consisting of, at most, a translated readme, license file, and wp-config-sample.php.
  • You have extensive custom changes consisting of other files, such as wp-content/languages/$locale.php or core modifications.

Here are the details on each:

  • If you have never had any custom changes and i18n.svn.wordpress.org is entirely empty for your locale, you do not need to do anything. Your release package will be created automatically for you. An example locale is en_GB.
  • If you have no custom changes for the current stable version (like 4.6), please ensure you have an empty branches/4.6/dist or tags/4.6/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.6 or tags/4.6 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.6/dist or tags/4.6/dist directory at i18n.svn.wordpress.org. (Having your files in only trunk/dist does not count.) 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 Rosetta as you have done in the past. For this, We are phasing out the ability to ship any customizations beyond license, readme, and wp-sample-config.php. This means you need to reach out to the WordPress core contributors to fold your modifications into WordPress core. You can start this process by creating a Trac ticket.

To summarize:

  • If all you have is a license, readme, and wp-config-sample.php (or no custom changes at all), everything will be automated for you if you follow the instructions above. Both language packs and release packages will automatically be created. If you are not at 100% at that time, then language packs and release packages will be created when you reach 100%. If you are later modify a translation (to fix a typo, for example), your language pack and release package will be regenerated.
  • If you have extensive custom changes, you will need to manually create a package via Rosetta as you have done in the past.

 

If you go to the releases screen on your Rosetta dashboard, you’ll see a new notice that explains what the system thinks your status is.

Top ↑

When are the packages built? When are the packages built?

Release packages and language packs for stable versions are built every 24 hours at midnight UTC (0:00). Packages for beta or release candidates are built every 6 hours.

Top ↑

How can I trigger a new automated build for my locale? 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.org is all that is needed.

Top ↑

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

No worries. First, create your SVN branches/tags. 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).
Or alternatively: Do a manual build via the release tool on your local site.

Top ↑

Is there a way to avoid creating new tags/branches which are empty? 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.)