Skip to content
Marc Laporte edited this page May 2, 2024 · 35 revisions

As of 2024-05-01, Cypht has 3 active branches:

About the process:

  • All commits start in master, and bug fixes can be backported to the stable branch
  • Critical bug fixes and security fixes can be backported to Old Stable
  • Releases to the stable branch can happen at any time (2.1.0, 2.2.0, ...). These releases will generally contain both bugs fixes and non-disruptive (and usually optional) new features, but there could be a 2.1.1 which would be just a bug fix or security fix
  • When there are significant changes, backward incompatible changes or major refactoring happens, a new major branch will be 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.: branch 2.x is End of Life (EoL) when Cypht 3.1.0 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.

Releases:

  • Patch releases 2.0.1, 2.0.2, etc. can be frequent and include bug fixes only
  • Minor releases 2.1.0, 2.2.0, etc. might be frequent and include enhancements, new features and fixes
  • Major releases like 3.0.0 will happen after significant changes, backward incompatible changes or major refactoring happens.

Medium term: