New release?

[Neustradamus]

Dear libsrtp team,

It is possible to release a new build before Debian 13 freeze?

Thanks in advance.

[pabuhler]

Hi, it's possible but do you have an actual date in mind ?

[Neustradamus]

@pabuhler: Thanks for your quick answer!

I have no date, but the first step is normally like each release 2025-01-12:

• https://release.debian.org/testing/freeze_policy.html

[pabuhler]

It would be possible to make a 2.7 release although there is only one real change since the 2.6 release. The 3.0 will not be ready.

[Neustradamus]

@pabuhler: It is better than nothing ^^

When 3.0 will be ready?

[AmosCalabrio]

I am also interested in a new version of libsrtp being released. My company prefers released versions to working off of main. We are looking for the WolfSSL support from #735 and other places.

[pabuhler]

Hi @Neustradamus & @AmosCalabrio , sorry for the late reply I have just been a bit unsure my self on when a release could be ready.
There are two main changes that I would like to complete before a v 3.0 will be release. That is to change the config API to be more flexible and remove the static initialization. At the moment I would target July as the most likely time frame for have these completed.
There will likely be a new 2.X release around the same time.

[Neustradamus]

@pabuhler: It is possible to have a new stable release before Debian 13?

• https://release.debian.org/testing/freeze_policy.html

[pabuhler]

@Neustradamus I thought it was already too late, but I see it is not so will start creating a new 2.x release now. It should be ready by next week.

[Neustradamus]

@pabuhler: I think that it will be good :)

Thanks in advance.

[pabuhler]

2.7 has now been released https://github.com/cisco/libsrtp/releases/tag/v2.7.0
3.0 will hopefully come by the end of June.

[Neustradamus]

@pabuhler: Thanks a lot!

Hope that @jonassmedegaard will update for Debian :)

[jonassmedegaard]

The new release has entered testing - thanks for alerting me by mentioning here, that helped. :-)

(apparently I do not have the power to close this issue, so will leave that to others...)

[pabuhler]

No problem, it is now closed.