Cut stable 1.0.0 release

[jack-berg]

Issue to track and discuss prerequisites to the first stable 1.0.0 release of opentelemetry-configuration

• Cut 1.0.0-RC release candidate and solicit feedback
• Should file_format follow semantic versioning? #2, addressed in Add a variety of key definitions surrounding stability #142
• Define stability guarantees for stable releases #89, addressed in Add a variety of key definitions surrounding stability #142
• Ensure all experimental properties are marked "experimental" #159
• make it possible to configure named resource detectors #119 (decide if blocking)
• Consider renaming OTLP certificate properties #160
• PushMetricExporter when using console, properties missing #242
• [ ] jaeger_remote needs clarity #238 We still need clarity on this but its no longer a blocker for stability since its been made an experimental feature.
• Align TLS configuration closer to Collector #322
• tls configuration options update #352
• Review schema from standpoint of meta schema #375
• Consider making log_level experimental #387
• Decide what to do about deprecated zipkin exporter and stability #428

This should mirror the declarative config stability project board, but an issue allows us to have an async discussion about scope, blockers, etc.

[jack-berg]

See also parent issue tracking overall stabilization of declarative config, of which opentelemetry-configuration is just one piece: open-telemetry/opentelemetry-specification#4374

[jack-berg]

#242 is blocking

[julealgon]

Could someone summarize what this "declarative configuration" idea is about, or provide a link that goes over the concept?

This is the first issue I see around this topic, and I was wondering if this will resolve some of my gripes with the current .NET implementation or if it's something completely unrelated.

[sureshg]

@julealgon i learned it from here - https://www.youtube.com/watch?v=u6svjtGpXO4

[jaydeluca]

@julealgon you can also read the spec