For translation

For any changes in the database

For improvements in the tips or contextual documentation provided to the user/admin/developers

For removals of unused or obsolete files.

For commits adding a new feature on Tiki

For the release process

For refactoring; changes the structure of the code (to make it cleaner or clearer), without changing its actual behaviour.

For security fix operations. If you feel you have reason to put this tag, please first contact security at tiki.org

For user experience improvements. It makes Tiki easier to use and understand (more details in https://dev.tiki.org/UX )

For updates of third party/vendor libraries

For branch merges, generally performed by the merge scripts

It is a change which may be disruptive. For example, changing the default value of an option.

For feature removals

Backport revision XXXX to current branch. Intended for committing a change already made in trunk to an earlier version. A backport reference should be added in front. For example, [bp/r61102][FIX] ... in a commit message to the branch branches/21x, means this fix is a backport of trunk revision 61102 to the next version of Tiki 21x. Depending on the period, backports are subject to an extra level of review so please read Quality Team and Where to commit first or ask on the mailing list or IRC if unsure.

Revert changes made by revision XXXXX. For example, adding [rb/r61102] ... in a commit message to the branch branches/21.x, means the change committed in revision 61102 are rolled back (removed, reverted) to the previous state, before r61102.

Suspicious code commits / merge requests

An enhancement; does not really add any feature, but makes things work better (e.g. look and feel, performance...)

Bug fixes of any sort

For merge requests done directly on a branch (not the common case). Means it needs to be cherry-picked into the master branch (so actually a forwardport, not a backport)

To be backported to all supported branches up to 21.xLTS (Security fixes only, EOL 2025-03)