Michal Čihař - Blog Archives for phpMyAdmin

Weblate 3.0

Weblate 3.0 has been released today. It contains brand new access control module and 61 fixed isssues.

Full list of changes:

  • Rewritten access control.
  • Several code cleanups that lead to moved and renamed modules.
  • New addon for automatic component discovery.
  • The import_project management command has now slightly different parameters.
  • Added basic support for Windows RC files.
  • New addon to store contributor names in PO file headers.
  • The per component hook scripts are removed, use addons instead.
  • Add support for collecting contributor agreements.
  • Access control changes are now tracked in history.
  • New addon to ensure all components in a project have same translations.
  • Support for more variables in commit message templates.
  • Add support for providing additional textual context.

If you are upgrading from older version, please follow our upgrading instructions, the upgrade is more complex this time.

You can find more information about Weblate on https://weblate.org, the code is hosted on Github. If you are curious how it looks, you can try it out on demo server. Weblate is also being used on https://hosted.weblate.org/ as official translating service for phpMyAdmin, OsmAnd, Turris, FreedomBox, Weblate itself and many other projects.

Should you be looking for hosting of translations for your project, I'm happy to host them for you or help with setting it up on your infrastructure.

Further development of Weblate would not be possible without people providing donations, thanks to everybody who have helped so far! The roadmap for next release is just being prepared, you can influence this by expressing support for individual issues either by comments or by providing bounty for them.

Weekly phpMyAdmin contributions 2018-W11

Last week was pretty quiet. The most interesting part was licensing issue with two factor authentication library we use. In the end the library was relicensed to MIT, what makes it compatible with pretty much anything.

I've spent some time on the Debian packages as well, I'm getting closer to make them work again, but there are still some issues to overcome.

Handled issues:

Weekly phpMyAdmin contributions 2018-W10

Last week was a bit quiet, I've spend some time on our infrastructure and doing reviews. There is still big pending task to update Debian packages and I will hopefully get to it this week.

Handled issues:

Weekly phpMyAdmin contributions 2018-W09

Last week I've continued on reviewing incoming pull requests and issues without coding much myself. It seems that amount of incoming issues is still quite big.

Handled issues:

Weekly phpMyAdmin contributions 2018-W08

Last week was mostly spent on reviewing pull requests. There is quite a lot them coming in and I always feel bad when we're not able to review incoming code in timely manner, but unfortunately it happens time to time.

Handled issues:

Weekly phpMyAdmin contributions 2018-W07

Last week was mostly spent on fixing issues with translations and improving our Docker container. That is now based on official PHP FPM image, so it will always get latest stable PHP instead of the one shipped by Alpine.

Besides that there was small, but important change in the motranslator library which no longer sets system locale (as it really has no good reason to do that). This change lead to releasing new major version of the library as it might need code changes for users who relied on this (what was the phpMyAdmin case).

Handled issues:

Weekly phpMyAdmin contributions 2018-W03

Last week was mostly spent on our infrastructure - I've migrated all virtual machines from old server to new one. This went pretty smoothly with about one hour delay during the migration. Everything now should work just fine and with considerably increased performance.

Handled issues:

Weekly phpMyAdmin contributions 2018-W02

Last week was equally spent on issues and infrastructure. There is quite serious regression in the 4.7.7 release which needs to be fixed (so far just the issue has been identified). In the same time our server is having hardware problems and we're preparing to migrate to new one (if everything goes well, the migration will be completed by the time you read this).

Handled issues:

Weekly phpMyAdmin contributions 2018-W01

First week of 2018 was a bit less intense on the code fixing side, but I've done some work on our infrastructure preparing for migration to the new server, which should be available as soon as Conservancy approves payments for it.

The new server will be located at Hetzner and you can check more details on the selection process in our wiki. The current server has been used for almost 10 years and is really showing it's age.

Handled issues: