Release Version 3.0.0
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- c
- Domain
- networking, security
Research direction
Start by reading the 3.0.0 goal and plan, then check the remaining tasks (#672, #588, #642), especially the CI test between versions and cleanup of unused repository files. This issue is a high-level release tracker, so identify a specific task and its linked issue before starting; done means completing that scoped task and updating its status.
Written by the indexing model from the issue text.
Description
Note: This is task definition is a work in progress
This is a high level issue to track architectural and coding effort to create and release the next major version of libSRTP.
Goal
Provide a cross platform C99 conformant SRTP library with a safe and flexible API.
Fix and close all issues that have been postponed due to ABI and behavioral restrictions.
Update build system and tools to be inline with current conventions.
Plan
Each PR should only change a single piece of functionality to help simplify reviews and traceability. Where possible test should not be refactored in the same commit as major code changes.
Tasks
- Create 2.x branch then prepare main for 3.x development
- Look into CI test between version
- Consider library name, currently libsrtp2.x, maybe libsrtp3.x? Check "so" name has correct version
- Clean out unused files from repo, there are a few old scripts that probably do not belong
- #671
- #790
- #672
- #220
- #322
- #569
- #588
- #579
- #441
- #642
- Update fuzzer with new api
- #716
- Dominant language
- C
- Stars
- 1.4k
- Forks
- 523
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 14
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cisco/libsrtp
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
cisco/libsrtp#816 · 4 comments ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
cisco/libsrtp#767 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
cisco/libsrtp#761 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
cisco/libsrtp#721 · 19 comments ·
Maintainers usually reply within 2 days
Similar issues
-
ecs_ptr_from_json does not free the buffer of a string longer than 256 bytes on two error pathsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SanderMertens/flecs#2444 ·
Maintainers usually reply within 1 day
-
Status: Opened
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
espressif/esp-eth-drivers#201 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
libsdl-org/SDL#16788 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cisco/ChezScheme#1110 ·
Maintainers usually reply within 1 day