Release Version 3.0.0

Open
#669 8 comments 0 reactions 0 assignees View on GitHub

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

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

enhancement

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cisco/libsrtp

All issues in cisco/libsrtp

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.