You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: RELEASING.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ A draft PR can be created, but before releasing consider the following:
16
16
17
17
* Are there any pending pull requests which should be included in the next release?
18
18
* Are they blockers?
19
-
* Are there any unresolved issues which should be resolved before the next release?
19
+
* Are there any unresolved issues which should be resolved before the next release? Check the release [blockers milestone](https://github.com/open-telemetry/opentelemetry-rust/milestones) for every release
20
20
* Bring it up at a SIG meeting, this can usually get some of these questions answered sooner than later. It will also
21
21
help establish a person to perform the release. Ideally this can be someone different each time to ensure that the
//! run with `$ cargo run --example logs-basic-in-memory
1
+
//! run with `$ cargo run --example logs-basic`
2
2
3
3
/// This example shows how to use in_memory_exporter for logs. This uses opentelemetry-appender-log crate, which is a
4
4
/// [logging appender](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/glossary.md#log-appender--bridge) that bridges logs from the [log crate](https://docs.rs/log/latest/log/) to OpenTelemetry.
@@ -8,15 +8,15 @@ use log::{error, info, warn, Level};
8
8
use opentelemetry_appender_log::OpenTelemetryLogBridge;
9
9
use opentelemetry_sdk::logs::{BatchLogProcessor,LoggerProvider};
0 commit comments