Create 2.1.0 release

[pabuhler]

This issue is used to track & announce the intention of a 2.1.0 release.
For details and status on the release please see the 2.1 release wiki page .

In the coming weeks all open issues & pull request will be evaluated for the 2.1.0 release and the "Version 2.1.0" milestone will be applied where applicable. If there are issues that you care about then now would be a good time to go poke them so they can be prioritized.

[pabuhler]

There are now two new libSRTP mailing list.

• libsrtp@lists.packetizer.com for general news / announcements / discussions. This is an open list, see
  https://lists.packetizer.com/mailman/listinfo/libsrtp for singing up.
• libsrtp-security@lists.packetizer.com for disclosing security issues to the libsrtp maintenance team. This is a closed list but anyone can send to it.

[briankwest]

Do you have an idea of when 2.1 will be released? I understand timeframes and deadlines aren't set in stone, I'd just like to know a general timeframe.

[pabuhler]

@briankwest I had hoped originally by the end of February, it's not looking to bad, maybe we can have a beta/release candidate at that time and try to finalize a week or two after. It would be really good to get some kind of feedback that things still work for people.

[briankwest]

Thank you for the response, we are looking to update libsrtp in FreeSWITCH and add MKI support shortly after the release.

/b

[rchan1611]

@pabuhler I hope #264 can be considered for 2.1.
libsrtp is actually generating non-RFC6188 compliant keystreams in the case of OpenSSL.

[mjerris]

any update on where we stand on release timing? Just trying to plan a bit on our testing.

[thisisG]

@mjerris - I think we're mainly waiting for set/get ROC in #289. Afaik there are no other major changes on the way except perhaps some portability fixes as mentioned in #229, but that might end up in a separate minor release.

[paulej]

Yeah, please review that one, if you can. I've added my comments, but other eyes on that would be helpful.

[pabuhler]

A 2_1_x_throttle branch has been created, this will be the base for the 2.1.0 release.
There are no outstanding issues blocking this release so if no new issues are found then the plan is to release 2.1.0 by 1st June.
It would be greatly appreciated if people take the time to test out this release now! Especially related to various platform support.

The 2.1.0 release contains several fixes that make it potentially incompatible with the current 1.5.x release. Due to this there will be an accompanying 1.6.0 release to ensure the there is compatibility between the 1.x series and the latest 2.x version for those that can not migrate to 2.1.0 for any reason.

[mjerris]

Any update on timeframe now that those last got in?

[pabuhler]

@mjerris Hopefully this week as there is very little feedback we trust that is working for all :-) .

[pabuhler]

Version 2.1.0 has now been released from the 2_1_x_throttle branch

Thanks you to every one that has contributed.

The following links are available for downloading:
Latest v2.1.0
Latest v2.1
Latest v2