GlotPress 2.2 Beta 1

The first beta of GlotPress 2.2.0 is now available!

This software is still in development. Consider setting up a test site just to play with the new version.

The beta can be downloaded from GitHub.

The focus of this release was to handle scripts and styles more efficient and to fix some minor bugs.

Breaking Changes

  • Change the slug of the Kyrgyz locale from ky to kir. (#550)

Bugfixes

  • Fix broken cancel link on project create form. (#547)
  • Fix native name of the Tibetan locale name from བོད་སྐད to བོད་ཡིག. (#539)
  • Fix extra entry in GP_Translation::translations(). (#516)
  • Merge similar strings to improve translation. (#535)
  • Refactor script and style registration to make them more reliable. (#476)
  • Update locale information for Kyrgyz to use correct data. (#550)

Features

  • Add locale information for the Latin version of Hausa. (#549)
  • Fix translations which are using the placeholder for tab characters. (#473)
  • Add gp_reference_source_url filter for the source URL of a project. (#522)
  • Provide minified assets. (#505)
  • Update JavaScript library for table sorting. (#502)

In this version 13 issues were solved and 19 Pull Requests were merged, a total of 65 commits.

Contributors of this release: Alexander Kirk, David Decker, Dominik Schilling, Greg Ross, Pedro Mendonça, Petya Raykovska, and Sergey Biryukov.

If you think you’ve found a bug, you can post to the issue tracker on GitHub.

The next release (RC1) is targeted for September 21, 2016.

Happy testing!

#473, #476, #502, #505, #516, #522, #535, #539, #547, #549, #550, #development, #release, #wordpress-plugin

Meeting starts this Thursday

It has been a long time goal to have a regular meeting but till now I couldn’t find the time that I would able to be there most of the time. After rethinking the time from comments, I decided to set up a weekly meeting at 12UTC on every Thursday starting this week.

This first meeting we will discuss how to notify Validators and translators for important changes. I just created two tickets for a Notification Center and for Favorites. This will help us out with sending out notifications and building up a user dashboard. In the next couple of days I will work on this so we can discuss the progress.

#142, #245, #294, #522, #562, #738, #769, #meeting