envoyproxy/envoy

community: develop stats deprecation policy

Open

#11,767 opened on Jun 26, 2020

View on GitHubContributor guide
 (5 comments) (2 reactions) (0 assignees)C++ (5,373 forks)batch import
area/communityarea/statshelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (PR metrics pending)

Description

Right now we do not have an explicit policy for how we deprecate and/or change stats. We should develop a policy that we can follow as we do with API and code deprecations.

Contributor guide

Research direction
Review existing API and code deprecation policies in the Envoy repository and propose a similar policy for stats. Consider the input from community discussions and align with current practices.
Tech stack
cpp
Domain
backend
Issue type
Documentation
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.
Half day
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
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70