Hello Daniel,

I will look with Xenofon this morning into it and backport the cmake fixes from 
the last days to 6.0 branch.

Cheers,

Henning

From: Daniel-Constantin Mierla via sr-dev <sr-dev@lists.kamailio.org>
Sent: Dienstag, 28. Januar 2025 17:16
To: Kamailio (SER) - Development Mailing List <sr-dev@lists.kamailio.org>
Cc: Xenofon Karamanos <x...@gilawa.com>; Daniel-Constantin Mierla 
<mico...@gmail.com>
Subject: [sr-dev] Re: Branching 6.0 series


Hello,



can you backport the cmake-related commits to branch 6.0 that you consider to 
be ready for it? It should be from last week, since the branch 6.0 was created. 
I was not sure what is ready or not, so I haven't gone through them. Being 
related to build tools, future cmake-related commits can also be backported to 
branch 6.0 if they apply for this release series.



Cheers,
Daniel


On 28.01.25 11:18, Xenofon Karamanos via sr-dev wrote:
Hey all,

Yeah we can keep for now the Makefiles until CMake is fully ready for used also 
in packaging.

As Henning said, RHEL and Fedora package seems to be working by Sergey apart 
from some minor json-c stuff currently.

There is still some work to be done for Debian-based and the modular packaging 
for the various groups to be used by Victor but hopefully soon it will be 
implemented.

Thanks,
Xenofon

________________________________
From: Henning Westerholt via sr-dev 
<sr-dev@lists.kamailio.org><mailto:sr-dev@lists.kamailio.org>
Sent: Tuesday, January 28, 2025 10:44
To: Kamailio (SER) - Development Mailing List 
<sr-dev@lists.kamailio.org><mailto:sr-dev@lists.kamailio.org>; Kamailio (SER) - 
Users Mailing List 
<sr-us...@lists.kamailio.org><mailto:sr-us...@lists.kamailio.org>
Cc: Henning Westerholt <h...@gilawa.com><mailto:h...@gilawa.com>
Subject: [sr-dev] Re: Branching 6.0 series

Hi Daniel,

releasing 6.0 tomorrow sounds good to me.

Regarding the package building with the cmake infrastructure: I think for RPM 
based distributions we are probably close, for Debian based distributions there 
seems to be more work open as discussed in the different GitHub issues.

Packages for 6.0 could be created with the old Makefile system, sure.

But we should remove the Makefiles in git master for release 6.1 then 
completely, just to finish the migration. The really old releases (Ubuntu 
16.04) with a too old cmake will be in 2026 then also end of life, so it should 
be fine.

Cheers,

Henning

> -----Original Message-----
> From: Daniel-Constantin Mierla via sr-dev 
> <sr-dev@lists.kamailio.org><mailto:sr-dev@lists.kamailio.org>
> Sent: Montag, 27. Januar 2025 18:38
> To: Kamailio (SER) - Development Mailing List 
> <sr-dev@lists.kamailio.org><mailto:sr-dev@lists.kamailio.org>;
> Kamailio (SER) - Users Mailing List 
> <sr-us...@lists.kamailio.org><mailto:sr-us...@lists.kamailio.org>
> Cc: Daniel-Constantin Mierla <mico...@gmail.com><mailto:mico...@gmail.com>
> Subject: [sr-dev] Re: Branching 6.0 series
>
> Hello,
>
> On 20.01.25 08:25, Daniel-Constantin Mierla via sr-dev wrote:
> > Hello,
> >
> > I think we should branch it on Wednesday, Jan 22, 2025, no matter on
> > what stage we are with cmake support. The old-Makefiles should be kept
> > anyhow (as they are or in a special folder with an easy way to recover
> > them), because there are many bits and pieces that can be discovered
> > later when more users.
> >
> > Because there were no many bugs reported to the C code specific to
> > 6.0, we can aim releasing on January 29, 2025, with old-Makefile still
> > to be used for tasks that are not yet covered by cmake.
>
> shall we still aim for releasing v6.0.0 on this upcoming Wednesday, January
> 29, 2025?
>
> We the old-Makefiles kept, it is doable, the wiki pages needs to be created 
> for
> this release series, which I can do tomorrow, as I waited to see if how it 
> should
> be the recommended method for compilation/installation.
>
> If the feeling is that we should wait, then probably the target date has to be
> shifted somewhere in the week starting on February 10, 2025, because
> Fosdem follows this weekend and then some countries have a week holiday
> break.
>
> If no other opinions and change of decision, the release will be done on
> Wednesday, with content using the old-Makefiles (to reuse existing
> tutorials) and reference to cmake variant when it is the case.
>
> 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 12-13, 2025, Berlin -- kamailioworld.com
>
> _______________________________________________
> Kamailio - Development Mailing List -- 
> sr-dev@lists.kamailio.org<mailto:sr-dev@lists.kamailio.org> To
> unsubscribe send an email to 
> sr-dev-le...@lists.kamailio.org<mailto:sr-dev-le...@lists.kamailio.org>
> Important: keep the mailing list in the recipients, do not reply only to the
> sender!
_______________________________________________
Kamailio - Development Mailing List -- 
sr-dev@lists.kamailio.org<mailto:sr-dev@lists.kamailio.org>
To unsubscribe send an email to 
sr-dev-le...@lists.kamailio.org<mailto:sr-dev-le...@lists.kamailio.org>
Important: keep the mailing list in the recipients, do not reply only to the 
sender!



_______________________________________________

Kamailio - Development Mailing List -- 
sr-dev@lists.kamailio.org<mailto:sr-dev@lists.kamailio.org>

To unsubscribe send an email to 
sr-dev-le...@lists.kamailio.org<mailto:sr-dev-le...@lists.kamailio.org>

Important: keep the mailing list in the recipients, do not reply only to the 
sender!

--

Daniel-Constantin Mierla (@ asipto.com)

twitter.com/miconda -- linkedin.com/in/miconda

Kamailio Consultancy, Training and Development Services -- asipto.com

Kamailio World Conference, May 12-13, 2025, Berlin -- kamailioworld.com
_______________________________________________
Kamailio - Development Mailing List -- sr-dev@lists.kamailio.org
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!

Reply via email to