Please note: SVN updates (for all versions of Tiki) will stop in January 2023 when Tiki18 reaches end of life, so you should get your updates from Git by then

Once you have read up on how to commit code, a very important decision is where to commit? Stable-LTS, Stable, Dev (trunk on SVN / master on Git), or experimental? You may want to checkout the Versions page. See also: Freeze and Slush and Git and SVN Combined Workflow


Quick overview intended to help to know where to commit to right now in most situations. See Branches section below for more detailed explanations.

Current status
  • All commits need to go in trunk/master first and then be backported/cherry-picked to the branches required.
    • For example if you want to make a fix to 18.x LTS, please commit the fix to trunk/master first then backport to 22.x, then 21.x and finally to 18.x. For more details, see the table below.
  • Upcoming releases:
    • 22.2, 21.4 LTS, 18.9 LTS, 15.10 LTS will be the next versions released.

Commit status and order for each open branch:

I want to commit to: What is allowed: Commit first to:
trunk/master (future 23x) Functional enhancements, new features, fixes and translations
22.x Minor enhancements, fixes and translations trunk
21.x Well tested minor enhancements, fixes and translations LTS 22.x
18.x Fixes only LTS 22.x and 21.x
15.x Critical fixes only LTS 22.x, 21.x and 18.x

The other branches are closed, and no releases are planned. So there is no point in committing there.

Branches Again


Devtrunk/master(will become 23.x branch in future) Most development (new features) happens here. New features, need to be functional, but don't need to be complete. In theory, should be releasable at any time. This is the place for refactoring. Cosmetic code changes should be done here.
Also: Update language stringsIf you must change the English version (but are not changing the meaning and so the translations are still valid, please use mass spelling correction. If you can't use that, just add to pending text corrections.. If you commit to trunk/master, and after you want to commit to a stable branch, please see how to merge a commit from trunk/master.
Stablebranches/22.x Minor safe enhancements, fixes and translations backported from master/trunk.
Stable LTSbranches/21.x Minor safe enhancements, fixes and translations backported from master/trunk.
Previous Stable LTSbranches/18.x Fixes only backported from 21.x
Legacy Stable LTSbranches/15.x Security only. Backport from 18.x.
Experimental branchesNow happening on GitLab forksAll developments for things that are not stable enough yet or just intended as proof of concept before the real work starts. These branches will never become a released branch directly, the author of the branch should create a Merge Request when it's ready (or a WIP MR before it's ready if you like.

Definition of "security-only" phase

  • The "security-only" of the LTS period is intended for security fixes, but could include a few bug fixes as well.
    • We will review security vulnerabilities reported to the Security Team
    • Publish a fix or a way to deactivate the feature.
      • If the included code doesn't have a patch for that version
  • What if a security vulnerability requires major code changes, that are not suitable for LTS?
    • We'll disable the feature via System Configuration so you can can choose to use it knowing the risks, decide not to use it, or upgrade.
  • The documentation at is kept up to date for more recent versions, so expect to see there some documentation about features not available in your Tiki.

Other notes

  • Commits to LTS must have been developed and tested previously on higher branches (at least trunk/master) unless they do not apply there (for example, a fix to a feature that was removed later). See here for more info.
  • The community will handle merges from stable to dev, with help from a merging script during Semi-automatic merging period
  • On stable branches, try to avoid any changes to the database as this complicates things and increases possibilities for errors. If you must, please see: Database Schema Upgrade
  • If you must change the English version (but are not changing the meaning and so the translations are still valid, please use Mass spelling correction. If you can't use that, just add to Pending text corrections
  • If we are close to a release, and you have a change with a risk of regression, try to consult the release manager.
  • There are some things that are black and white and there are many shades of gray. In case of doubt, ask on the Dev Mailing List


There are no more planned releases of versions prior to 12, as well as versions 13, 14, 16, 17 and 19. If you are running one and commit a fix , please merge manually your fix to the appropriate branch.