From openSIPS

Development: Development


OpenSIPS Release Policy

The OpenSIPS software release policy is designed in such a way to be open (anyone can get involved), reliable (know what to expect) and transparent (to the whole community).

Major Release Flavors

The flavor of a release affects both its content (choice of features), as well as its maintenance timeline. There are two flavors of major releases:

Standard Releases

Long-Term Supported Releases (LTS)

This "standard vs. LTS" release model aims to strike a good balance between shipping more complex, time-consuming and high-risk features (e.g. the major rework for async support in 2.1, major rework for switching to JSON-RPC communication in 3.0, the major module function parameter rework in 3.1, etc.), as well as taking the time to test the codebase for either performance regressions or key code bottlenecks which could highly benefit from optimization. Experienced VoIP developers, early adopters and OpenSIPS power users should opt for the standard releases, while users looking for a battle-tested, stable and better supported release should choose a long term supported release.

By supporting a version, we understand troubleshooting, fixing bugs, and backporting various new fixes from the more recent OpenSIPS versions. Also, we will take care to maintain packages and tarballs for the supported releases.

Once an OpenSIPS release moves to unsupported status, it will not get any new bug fixes, re-packaging or new tarballs.

Retrieved from
Page last modified on November 06, 2020, at 05:19 PM