1.0 Release tracking

[dmitryax]

This issue is for tracking progress towards reaching OTel Collector Core stability.

The proposed approach is to split Collector packages into more modules which can be gradually declared 1.0 with multimod tool. The plan on how to break down Collector packages into modules that have minimal dependencies on each other is in progress.

Currently we are working towards bringing model module to 1.0 which is tracked under this milestone: https://github.com/open-telemetry/opentelemetry-collector/milestone/24

[pavolloffay]

@dmitryax @bogdandrutu @tigrannajaryan any update on the collector 1.0/GA release?

[dmitryax]

@pavolloffay https://github.com/open-telemetry/opentelemetry-collector/milestone/24 is pretty close to be done. We will release model 1.0 first, then will be working on other modules

[Mario-Hofstaetter]

Dear all, milestone https://github.com/open-telemetry/opentelemetry-collector/milestone/24 looks finished.

Is there any roadmap when to expect a stable 1.0 release of OTELCOL and contrib?
Releases are currently coming at a high cadence, few are worth rolling out in our case.

[dmitryax]

Is there any roadmap when to expect a stable 1.0 release of OTELCOL and contrib?

We are actively working on this, but there is limited capacity. pdata 1.0 will be likely released as part of the next release, component 1.0 is in progress and will be released soon after that. Other parts of the collector will go next. No specific timeline beyond that.

Releases are currently coming at a high cadence, few are worth rolling out in our case.

This is expected, we need to run through a lot of changes to stabilize the API for 1.0.

[Mario-Hofstaetter]

Thanks for the quick response @dmitryax

This is expected, we need to run through a lot of changes to stabilize the API for 1.0.

From a otelcol user perspective, how many breaking changes are expected regarding operating otelcol?
e.g. breaking changes in yaml config of components, ...

I guess.. until its stable anything may change?

[dmitryax]

From a otelcol user perspective, how many breaking changes are expected regarding operating otelcol?
e.g. breaking changes in yaml config of components, ...

Breaking changes for 1.0 release are mostly applied to developer API. User API (config interface) stability is defined for each component independently, e.g. https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/otlpexporter is stable for metrics and traces and beta for logs, it means that no breaking changes are expected there. See https://github.com/open-telemetry/opentelemetry-collector#stability-levels

[codeboten]

Closing this issue in favour of #9375