** Changed in: mahara
Status: Fix Committed => Fix Released
--
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 for
** Changed in: mahara
Status: In Progress => Fix Committed
** Tags added: nominatedfeature
--
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
Hi Dajan,
Currently we only generate lagpack tarballs for the _STABLE of a branch,
see http://langpacks.mahara.org/
This means if one is upgrading from say 15.10.1 to 15.10.2 but the
latest branch version is 15.10.6 they would get the 15.10.6 specific
langpack and there could be changes in the la
** Changed in: mahara
Milestone: None => 17.04.0
--
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 edit
Could we imagine that, as it is the case with Moodle, this script
becomes part of the upgrade.php script and automatically upgrade the
langpack to the latest version of the release at each upgrade?
The upgrade script would look at the installed langpacks and upgrade
them with the latest version.
5 matches
Mail list logo
