Lifecycle

Cypht has two active branches:

• Dev: Master from https://github.com/cypht-org/cypht/commits/master
• For stable releases, we'll use a cycle like this: 2.0, 2.1, 2.2, 3.0, 3.1, etc. (Previously, it was 1.3.0, 1.3.1, 1.4.0, 1.4.1)

About the process:

• We follow the general principles of https://semver.org/
• All commits start in master, and bug fixes can be backported to the stable branch.
• Releases to the stable branch can happen at any time (2.1, 2.2, ...).
• Every 6 to 8 months, a new branch is created from master and it becomes the new stable branch. Because .0 releases can sometimes be buggy, the previous stable branch is supported until the x.1 release of the next branch (). Ex.: 2.x is End of Life (EoL) when Cypht 3.1 is released.
• Historical information: Until 2023, Cypht mostly had just a master branch which was kept quite stable, and infrequent stable releases were made from this, like 1.3.0. But these branches didn't really live / receive bug fixes.

Medium term:

• Cypht is the webmail used for Tiki Wiki CMS Groupware. Part of the Tiki community is actively involved in Cypht development. While Cypht remains an independent project, it is to be expected that Tiki will influence Cypht for future development. For example:
  • The Cypht license has been aligned to be the same as Tiki, to facilitate integration and code sharing. It was GPL and became LGPL.
  • In the future, we'll likely implement some long term support (LTS) versions like Tiki.
  • We'll converge the dependencies