Support Branches

Support branches are created in Git after every minor release. They are maintenance versions of midPoint (see Release Process) and they contain the most recent bugfixes. In support branches, bugfixes accumulate until another major release is done.

Support branches do not contain new features planned for the upcoming major or minor releases. Those are kept in the current main development branch (currently master branch). Note that while support branches are typically reasonably stable, the code in the master branch may not be.

Support branches are maintained as branches in the midPoint Git repository. They follow this naming convention:

"x.y" stand for the last minor release. Once you have the repository, you can switch the workspace to a support branch by using the checkout command. For example:

As individual Git tools may vary, see the documentation of your Git tool for details.

Once the workspace is switched to a support branch, you can build the system in the usual manner. Follow the instructions in Installing midPoint Development Snapshot - Source Code. Only instead of master, use the support-4.8 branch name, or another, depending on the current release.

After you make a new commit into the branch, i.e. you add new content, Jenkins (build server) automatically builds the snapshot version and places the binary into the nexus.evolveum.com repository. Binaries are available also at the download page.