GiellaLT Documentation

GiellaLT provides rule-based language technology aimed at minority and indigenous languages

View GiellaLT on GitHub

Page Content

Speller release procedure

Speller release step by step

  1. update the speller version number constant SPELLERVERSION in, using semantic versioning:
    • MAJOR version = incompatible changes, and going from beta to release (from 0.x.x to 1.x.x)
    • MINOR version = new / more words
    • PATCH version = actual bug fixes
  2. make sure that the new version is also recorded in manifest.toml, either by editing manually, or by running make after changing
  3. commit the changes in both and manifest.toml
  4. create a new GIT tag for the release, using the following pattern:
    • v + version string from previous step. If the version string is 1.2.3, the tag should be v1.2.3
  5. push commits and tag to GitHub.

CI + CD will do everything, including releasing the updated speller to the pahkat server, as long as the GIT tag is properly set.

The pahkat client installed as part of Divun Manager will then ensure that the new speller version is automatically installed on user machines on the next server poll.

Re-release on error

If something caused the CI or CD to fail, fix the the issue, and add the same GIT tag to the new revision, the one containing the bug fixes. You will be told there already exists an identical tag, so force push to override the old one.

As long as the new version did not reach users, there is no need to update the version string. But if the buggy version DID get released, then you MUST start from the top, and create a new version.

Tags, version strings and Divvun Manager channels

Divvun Manager has three channels to install from, selectable from the preferences (the actual text may be localised):

The channels are populated as follows:


Any keyboard or language model commit that is:


Any keyboard or language model commit that is:


Any keyboard or language model commit. That is, Nightly will always contain the latest successful build.

Automatic updates in Divvun Manager

When an update is released, in any of the channels according to the rules above, older packages installed from the same channel will be updated automatically: a beta release will automatically update an older, installed beta release of the same package, a stable release will automatically update an older stable release, and so on.