Release Schedule

We work on a time based release cycle.

All code is developed in the open, from multiple developers all around the world. This code is separated into adding new features, and fixing bugs.

New features are released every six months, these are the x.x.0 releases, (3.2.0, 3.4.0, 3.6.0 etc).

Every month we release a bugfix release also, these are the 3.4.1, 3.4.2 etc releases.

So how does code get into Koha? Well it’s pretty simple, and all contributors follow the same rules which makes it easy. Here’s a quick run down.

A bug/enhancement is submitted by the ‘bug reporter’.
A patch is submitted by the ‘patch writer’.
(optional) RM pushed it as a QA branch.
The patch is tested and signed off by the ‘patch signer’.
The patch is tested by the QA manager, patch status is set to Passed QA
The patch is tested and signed off by RM
If the patch passes, it is pushed into master by the RM, status is set to Patch Pushed.
The bug is marked resolved by the ‘bug closer’.
The bug is closed when a release is made containing that patch.