Hello,
last week several developers went to Dusseldorf for the Kamailio Devel Meeting for two fruitful days working on merging some of the pull request, address many reported issues, building a new deb packaging infrastructure, as well as add new features.
Among achievements: reviewing/merging a couple of PRs, including merging a new module; pull request to use stdatomic; completing the building of debs with cmake; start of creating the new platform for deb building; proper support for async sql queries with no connection available at start up; more modules not destroying structures at shut down to avoid races; archiving a few modules ...
During a video conference with other main developers, it was also discussed about the roadmap to the next major release series, respectively Kamailio v6.1.x, agreeing more or less to continue the development for about 2-3 weeks to allow people to still contribute new features, then enter the testing phase.
Based on that, I would propose:
- freeze the development at the beginning of January 7, 2027 (to be after the winter/season holidays, before many devs might be offline) - testing phase as needed for 4 to 6 weeks - release likely to be by mid of February or slightly later
The new features have to be pushed to the git repository or made pull requests by freeze date.
Should anyone want to suggest alternatives, just propose them to sr-dev mailing list to be discussed further with the developers.
Cheers, Daniel
Hello,
with Kamailio 6.0.5 scheduled for this week, Thursday, January 8, 2026, I would prefer to delay with one day the freezing date for the next major release series Kamailio v6.1.x, so it is at the end of same day (January 8, 2026) -- it makes things easier to do the versioning updates on Friday morning, after the pressure of testing/release the current stable is gone.
Following the past releases approach, the existing pull requests can still be merged during the first part of the testing phase, till the moment the git branch 6.1 is created, therefore if anyone still wants to add new features to 6.1.x, make sure to push them to git repository when already having a developer access or create the pull requests till freezing announcement (till the end of January 8, 2026). Work on related tools and documentation, as well as completing/tuning the new features of 6.1.x, are also allowed during the testing phase.
Cheers, Daniel
On 15.12.25 12:58, Daniel-Constantin Mierla wrote:
Hello,
last week several developers went to Dusseldorf for the Kamailio Devel Meeting for two fruitful days working on merging some of the pull request, address many reported issues, building a new deb packaging infrastructure, as well as add new features.
Among achievements: reviewing/merging a couple of PRs, including merging a new module; pull request to use stdatomic; completing the building of debs with cmake; start of creating the new platform for deb building; proper support for async sql queries with no connection available at start up; more modules not destroying structures at shut down to avoid races; archiving a few modules ...
During a video conference with other main developers, it was also discussed about the roadmap to the next major release series, respectively Kamailio v6.1.x, agreeing more or less to continue the development for about 2-3 weeks to allow people to still contribute new features, then enter the testing phase.
Based on that, I would propose:
- freeze the development at the beginning of January 7, 2027 (to be after the winter/season holidays, before many devs might be offline) - testing phase as needed for 4 to 6 weeks - release likely to be by mid of February or slightly later
The new features have to be pushed to the git repository or made pull requests by freeze date.
Should anyone want to suggest alternatives, just propose them to sr-dev mailing list to be discussed further with the developers.
Cheers, Daniel
Hello,
quick reminder that by the end of today (Jan 8, 2026), the development branch is going to be frozen and testing phase for next major release series 6.1.x starts.
Therefore, the new features to existing Kamailio components that are wanted to be part of 6.1.x have to be pushed to git repository or made PRs before freezing announcement.
Cheers, Daniel
On 05.01.26 21:27, Daniel-Constantin Mierla wrote:
Hello,
with Kamailio 6.0.5 scheduled for this week, Thursday, January 8, 2026, I would prefer to delay with one day the freezing date for the next major release series Kamailio v6.1.x, so it is at the end of same day (January 8, 2026) -- it makes things easier to do the versioning updates on Friday morning, after the pressure of testing/release the current stable is gone.
Following the past releases approach, the existing pull requests can still be merged during the first part of the testing phase, till the moment the git branch 6.1 is created, therefore if anyone still wants to add new features to 6.1.x, make sure to push them to git repository when already having a developer access or create the pull requests till freezing announcement (till the end of January 8, 2026). Work on related tools and documentation, as well as completing/tuning the new features of 6.1.x, are also allowed during the testing phase.
Cheers, Daniel
On 15.12.25 12:58, Daniel-Constantin Mierla wrote:
Hello,
last week several developers went to Dusseldorf for the Kamailio Devel Meeting for two fruitful days working on merging some of the pull request, address many reported issues, building a new deb packaging infrastructure, as well as add new features.
Among achievements: reviewing/merging a couple of PRs, including merging a new module; pull request to use stdatomic; completing the building of debs with cmake; start of creating the new platform for deb building; proper support for async sql queries with no connection available at start up; more modules not destroying structures at shut down to avoid races; archiving a few modules ...
During a video conference with other main developers, it was also discussed about the roadmap to the next major release series, respectively Kamailio v6.1.x, agreeing more or less to continue the development for about 2-3 weeks to allow people to still contribute new features, then enter the testing phase.
Based on that, I would propose:
- freeze the development at the beginning of January 7, 2027 (to be after the winter/season holidays, before many devs might be offline) - testing phase as needed for 4 to 6 weeks - release likely to be by mid of February or slightly later
The new features have to be pushed to the git repository or made pull requests by freeze date.
Should anyone want to suggest alternatives, just propose them to sr-dev mailing list to be discussed further with the developers.
Cheers, Daniel
-- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, May 7-8, 2026 - Berlin, Germany -- kamailioworld.com
-
Daniel-Constantin Mierla