Document upgrade and compatibility policy

jaegertracing / documentation

Documentation/website for the Jaeger Distributed Tracing project.

https://jaegertracing.io/

Apache License 2.0

68 stars 166 forks source link

Document upgrade and compatibility policy #117

Open yurishkuro opened 6 years ago

yurishkuro commented 6 years ago

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

jkowall commented 6 days ago

I think we should provide similar advice to the first bullet, as there is less impact with this method (query first). Since we are using Otel there is no real "agent" but instead collector role (including Kafka which likely needs to have both upgraded together).

I do not see us making schema changes at this point, but should we want to normalize the schema to Otel versus OT we might make this change.

I would see this being part of a FAQ.

I should also remove jaeger-agent from the v2 FAQ :)

yurishkuro commented 5 days ago

We have some compatibility rules in https://github.com/jaegertracing/jaeger/blob/main/README.md#version-compatibility-guarantees