Add version numbers to language packs

Bug #1184465 reported by Aaron Wells
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
Triaged
Wishlist
Unassigned

Bug Description

As I touched on in https://bugs.launchpad.net/mahara/+bug/1180544 , there's currently no way for a user looking at the langpacks site ( http://langpacks.mahara.org/ ) to tell whether there's been an update to their language pack.

Therefore, it would be useful if we added version numbers to the language packs. These could be placed in lang/langconfig.php, something like this:

$string['release'] = '1.7.1'; // The Mahara release number this langpack was created for
$string['version'] = '2013052700'; // Incremented on each new release of the langpack, using the current date.

And the name of the langpack file could be changed to something along the lines of "vi-1.7_STABLE-2013052700.tar.gz".

A related idea would be to have specific langpack releases tied to Mahara minor version releases, to support the case where a language string's name is changed in a minor version. In that case, you wouldn't want to upgrade your langpacks before your Mahara version has been upgraded. In that case you'd want langpack releases for each minor version, as well as maybe a "nightly" langpack release.

vi-1.7.3.tar.tgz
vi-1.7.4.tar.tgz
vi-1.7_STABLE-2013052700.tar.gz

Tags: langpacks
Revision history for this message
Aaron Wells (u-aaronw) wrote :

On a related note, it would probably be handy if there was an admin page that listed the currently installed languages and what their release and version numbers are. This may require adding another language string to langconfig.php with the name of the language.

Changed in mahara:
status: New → Confirmed
Aaron Wells (u-aaronw)
description: updated
Changed in mahara:
assignee: Son Nguyen (ngson2000) → nobody
milestone: none → 17.04.0
Revision history for this message
Robert Lyon (robertl-9) wrote :

Useful to target this to 17.04.1 as well as 17.10

Most of the changes will be external to Mahara itself - dealing with creation/saving of langpacks

The bit Mahara will care about is the installing langpacks via CLI. Currently it just fetches the langpack based on the branch version ones mahara is on, version 16.04.

Going forward it would fetch the branch version instead, eg 16.04.2

Changed in mahara:
milestone: 17.04.0 → 17.10.0
Robert Lyon (robertl-9)
no longer affects: mahara/17.04
no longer affects: mahara/17.10
Changed in mahara:
milestone: none → 18.04.0
Robert Lyon (robertl-9)
Changed in mahara:
milestone: 18.04.0 → 18.10.0
Changed in mahara:
milestone: 18.10.0 → none
Changed in mahara:
assignee: Cecilia Vela Gurovic (ceciliavg) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.