Re: [sr-dev] Pull request development workflow

Hello, the stable branches have no-new-feature release policy. It means that once we create a branch for a new series for stable releases, only bug fixes and documentation improvements are committed in the branch. The new features in the master branch will be part of the next major release series, respectively 5.0, which is in devel frozen state (testing), by end of this month/beginning of next, we will create the branch 5.0, the first release out of it, v5.0.0, to be out few weeks later. The last stable branch 4.4 was created before the pull requests you linked in your email. They were not backported to v4.4, they will be in v5.0. Not porting new features ensure a better stability of the release branches. We try to do a new major release each 8-12 months, usually around 10, so people don't wait long for new features to get into a stable release. If still not clear or have other questions, don't hesitate to ask more. It's important to understand properly the release policies. Cheers, Daniel On 18/01/2017 09:06, Luis Martin Gil wrote: -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com