Stabilize Logs

[jack-berg]

The logs bridge API / SDK specification is approaching stability. This issue is to discuss and track the process of stabilizing various otel java log components.

Components to stabilize:

• promote opentelemetry-api-logs API opentelemetry-api Promote log API / SDK to stable #5341
• mark opentelemetry-sdk-logs as stable Promote log API / SDK to stable #5341
• promote opentelemetry-exporter-otlp-logs to opentelemetry-exporter-otlp Merge otlp logs #5432
• promote opentelemetry-sdk-logs-testing to opentelemetry-sdk-testing Merge sdk logs testing #5431

Other tasks:

• Decide whether we want a RC. While we provided a RC for metrics and traces, it may not be necessary for the logs bridge API given that its not meant to be consumed by end users, and opentelemetry-java-instrumentation is the primary consumer.
• Enable otlp exporter by default in opentelemetry-sdk-extension-autoconfigure Enable otlp logs by default #5433
• Update default BatchLogRecordProcessor config to match spec Align BatchLogRecordProcessor defaults with specification #5364

[jack-berg]

Decide whether we want a RC.

In the 4/20 Java SIG we discussed treating the next 1.26.0 release as a RC. 1.26.0 would be released with separate logs artifacts as it is today, with those APIs in their final form with the exception of which artifact they live in. From 1.26.0 to 1.27.0 we'd merge #5341 (and additional PRs to merge logs testing, and the otlp log exporter).

@jkwatson WDYT?

[jack-berg]

All subtasks are completed. Marking this as complete.