Pablo Baeyens

[chore][docs/release] Clarify that we will not make any minor releases outside of the schedule

10

#### Description Proposes that we will not make minor releases out of schedule and that changes to existing dates in the schedule need at least two approvals.

[exporterhelper] Enable block_on_overflow by default

2

#### Description This is a test to see how our test suite behaves with `block_on_overflow` set to `true`

[chore][test] Prove that unmarshal method gets called for a map wrapper

1

#### Description #### Link to tracking issue Fixes # #### Testing #### Documentation

#13783 introduced an option to disable an optional section. We should instead use a generic soltuion for enabling/disabling

Add optional display name to metadata.yaml

2

From @jaydeluca in #otel-ecosystem-explorer ([ref](https://cloud-native.slack.com/archives/C09N6DDGSPQ/p1761933616276329)): > i'm curious what you would think about the feasibility of introducing an optional "display_name" field to the collector metadata components? for example, the [basicauthextension](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/basicauthextension)...

This is a [testing requirement for stable components](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#testing-requirements). I have suggested using [codspeed.io](https://codspeed.io/) for this and using [Go benchmarks](https://pkg.go.dev/testing#hdr-Benchmarks) to do this. I believe the steps should be: - [...

We have benchmarks results available on https://opentelemetry.io/docs/collector/benchmarks/, however there are several issues with this page: 1. The page is not easily discoverable: [in the last month it got fewer than...

To make sure reviewers are aware of the changes that relate to e.g. configuration changes listed on [the component stability guidelines](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md) we can try and have some automation that on...

Validate codeowner activity and presence

5

Codeowner activity is [part of the graduation criteria for components](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#graduation-criteria). We should have a way to validate these automatically (maybe triggered by a command?)

This is a [documentation requirement for stable components](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#documentation-requirements-2). Relates to #9769 (but does not necessarily imply it). There have been multiple iterations of this, see #13726, #13155, #10694, #10376 and...