SVN updates (for all versions of Tiki) will stop in January 2023. This coincides with when Tiki18 reaches end of life. However, even if you use another version (like Tiki 21x) from SVN, you will stop getting updates because the Git and SVN combined workflow will be retired. You should get your updates from Git. See also: Tiki Version control history.


Tiki was first released in October 2002 using CVS on SourceForge

The path to the source code was:


The Tiki project transitioned to Subversion (SVN) as of Tiki2, remaining at SourceForge. The platform was called Alexandria (internal name, not really promoted)

The path to the source code was (now inactive)

The Tiki Remote Instance Manager (TRIM) project was started, and it offered a tool to convert a CVS instance to SVN.


Still at SourceForge, the source code moved to the Allura platform

The Allura project was here:

And later became Apache Allura

(from previous "Alexandria" platform). Ref.: Update from SVN pre 2013

The path to the source code became:


In May 2018, during the Tiki19 development cycle, a Git and SVN combined workflow using (SubGit) was implemented. The canonical source code is still SVN on SourceForge, but contributors progressively start collaborating via Git, on GitLab

The path to the source code became:

After a while (not sure when), it was agreed no one should commit on SVN anymore, because 2-way sync would sometimes break.

In November 2018, Tiki Manager started as a revamp/fork/major upgrade of TRIM. Tiki Manager supports SVN and Git.


Git becomes the default in Tiki Manager:


Shortly after January 2023, the Git and SVN combined workflow will be retired, and there will no longer be any updates to SVN (except perhaps to add warnings to migrate). is the canonical repo.

Other history: