Changelog refactoring (open-telemetry#2632)

Author: cijothomas

.cspell.json

@@ -49,6 +49,7 @@
         "Kumar",
         "Lalit",
         "LIBCLANG",
+        "MILLIS",
         "msrv",
         "mykey",
         "myvalue",
@@ -68,6 +69,8 @@
         "rstest",
         "runtimes",
         "rustc",
+        "rustls",
+        "semconv",
         "serde",
         "shoppingcart",
         "struct",

opentelemetry-appender-tracing/CHANGELOG.md

@@ -5,7 +5,6 @@
 - Bump msrv to 1.75.0.
 - New experimental feature to use trace\_id & span\_id from spans created through the [tracing](https://crates.io/crates/tracing) crate (experimental_use_tracing_span_context) [#2438](https://github.com/open-telemetry/opentelemetry-rust/pull/2438)
 
-
 ## 0.27.0
 
 Released 2024-Nov-11

opentelemetry-http/CHANGELOG.md

@@ -3,7 +3,7 @@
 ## vNext
 
 - Bump msrv to 1.75.0.
-- Add "internal-logs" feature flag (enabled by default), and emit internal logs.
+- Add "internal-logs" feature flag (enabled by default), and emit internal logs via `tracing` crate.
 - Add `HttpClient::send_bytes` with `bytes::Bytes` request payload and deprecate old `HttpClient::send` function.
 
 ## 0.27.0

opentelemetry-jaeger-propagator/CHANGELOG.md

@@ -4,7 +4,6 @@
 
 - Bump msrv to 1.75.0.
 
-
 ## 0.27.0
 
 Released 2024-Nov-11

opentelemetry-otlp/CHANGELOG.md

@@ -14,14 +14,13 @@
   and `MetricExporter::new(..)` method. Use
   `MetricExporter::builder()...build()` to obtain `MetricExporter`.
 - The HTTP clients (reqwest, reqwest-blocking, hyper) now support the
-timeout internal configured in below order
-  - Signal specific env variable `OTEL_EXPORTER_OTLP_TRACES_TIMEOUT`, 
+  export timeout interval configured in below order
+  - Signal specific env variable `OTEL_EXPORTER_OTLP_TRACES_TIMEOUT`,
   `OTEL_EXPORTER_OTLP_LOGS_TIMEOUT` or `OTEL_EXPORTER_OTLP_TIMEOUT`.
   - `OTEL_EXPORTER_OTLP_TIMEOUT` env variable.
   - `with_http().with_timeout()` API method of
 `LogExporterBuilder` and `SpanExporterBuilder` and `MetricsExporterBuilder`.
-  - The default interval of 10sec is used if none is configured.
-
+  - The default interval of 10 seconds is used if none is configured.
 
 ## 0.27.0
 

opentelemetry-proto/CHANGELOG.md

@@ -2,7 +2,6 @@
 
 ## vNext
 
-- Update proto definitions to v1.4.0 [#2315](https://github.com/open-telemetry/opentelemetry-rust/pull/2315)
 - Bump msrv to 1.75.0.
 - Update proto definitions to v1.5.0 [#2439](https://github.com/open-telemetry/opentelemetry-rust/pull/2439)
 - Feature flag "populate-logs-event-name" is removed as no longer relevant.

opentelemetry-sdk/CHANGELOG.md

@@ -3,10 +3,8 @@
 ## vNext
 
 - Update to [v1.29.0](https://github.com/open-telemetry/semantic-conventions/releases/tag/v1.29.0) of the semantic conventions.
-- Update to [v0.11.0](https://github.com/open-telemetry/weaver/releases/tag/v0.11.0) of the semantic conventions.
 - Bump msrv to 1.75.0.
 
-
 ## 0.27.0
 
 Released 2024-Nov-11

opentelemetry-semantic-conventions/CHANGELOG.md

@@ -7,12 +7,15 @@
   Additionally, the service name needs to be set on the tracer provider.
 
   Previous Signature:
+
   ```rust
   let tracer = opentelemetry_zipkin::new_pipeline()
       .with_service_name("trace-demo")
       .install_simple()?;
   ```
+  
   Updated Signature:
+  
   ```rust
   let exporter = ZipkinExporter::builder()
       .build()?;