jaegertracing / jaegertracing/documentation

Document upgrade and compatibility policy

Open
#117 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
84
Forks
192
Avg merge
12h 25m
Merged PRs (30d)
4

Description

- the order of upgrades of backend components is always: query, collector, agents
- compatibility guarantee between backend components: V-1 and V only
- compatibility between clients and backends: by default backend should be compatible with all clients, but there may be future exceptions

Contributor guide

Open the contributing guide

Research direction

Start by locating the Jaeger documentation page covering backend upgrades and compatibility; no specific file or test is named in the issue. Document the upgrade order, the V-1/V backend guarantee, and the default client-backend compatibility policy, including the noted possibility of future exceptions.

Written by the indexing model from the issue text.

Assessment

Tech stack
hugo
Domain
backend, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.