mahara-contributors team mailing list archive

[Robert Lyon <robertl@xxxxxxxxxxxxxxx>]

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

** Also affects: mahara/17.04
   Importance: Medium
       Status: Confirmed

** Also affects: mahara/17.10
   Importance: Undecided
       Status: New

** Changed in: mahara/17.10
   Importance: Undecided => Medium

** Changed in: mahara/17.10
       Status: New => Confirmed

** Changed in: mahara/17.10
    Milestone: None => 17.04.1

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1184465

Title:
  Add version numbers to language packs

Status in Mahara:
  Confirmed
Status in Mahara 17.04 series:
  Confirmed
Status in Mahara 17.10 series:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1184465/+subscriptions