envoyproxy/envoy

Consider abbreviated security release process for issues found on master (not yet in any release)

Open

#11,167 opened on May 12, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/communityarea/securityhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Envoy has a security release process. However, it doesn't fit well for issues found on master, and not yet in any release.

We should consider creating an abbreviated process for notifying interested parties, and releasing the fix in a shorter window of time.

Some discussion on the issue: https://github.com/envoyproxy/envoy/pull/11148#discussion_r423221002

Contributor guide

Research direction
Study the current Envoy security release process and identify its steps. Propose a streamlined version for issues on master that are not yet in any release, focusing on shorter notification and release timeline.
Tech stack
ccpp
Domain
securitybackendinfrastructure
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20