Trask Stalnaker

Renamed to "repository practices". Other naming ideas very welcome!

I didn't end up needing the behavior, so just reporting doc bug

> the thread pool issue still remain OpenTelemetry exporters are batched and single-threaded, can you elaborate on what kind of thread pool issue you are seeing?

Closing as there does not appear to be engagement from the necessary folks in order to move this forward at this time.

> As mention on Slack. I think that the entire content of this section should be moved one level up, into the Java landing page (or it's own Comparing page)....

check out https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md: > **Warning** > > Existing database instrumentations that are using [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/database/database-spans.md) (or prior): > > * SHOULD NOT change the version of the database...

> I would rather first have a PR which bumps semconv to `v1.24.0` would this go against the semconv recommendation? > SHOULD NOT change the version of the database conventions...

> I thought that breaking changes started since v1.25.0. But I need to double check it later ah, if that's the case then no problem, since that guidance was just...

@prestonvasquez `OTEL_SEMCONV_STABILITY_OPT_IN` is a comma-separated list of values, see https://github.com/open-telemetry/semantic-conventions/blob/main/docs/database/database-spans.md > * SHOULD introduce an environment variable `OTEL_SEMCONV_STABILITY_OPT_IN` > in the existing major version which is a comma-separated list of...

> @trask Would you mind reading the PR description and letting me know if the proposal is in line with the spirit of this requirement? my recommendation would be to...