[toc] central jump off point for release process / documentation

[dims]

For the CNCF Graduation issue, we are looking into release process for various repositories:
cncf/toc#1739

It looks like there isn't a central place where we can find information as it is spread across all the repos:
https://github.com/search?q=org%3Aopen-telemetry+path%3Areleas*.md&type=code&p=1

Is there some common things across these? Like who makes the release? when do you make the release? how do you figure out who will handle the next release?

May be a table with links to individual processes for each repo will be a good start? and document some of the common things / themes that cut across these repos would be good information to have?

thanks,
Dims

[dims]

cc @austinlparker @TheFoxAtWork

[austinlparker]

We can certainly look into providing this!

[dims]

@austinlparker first step is to reflect current state of affairs. then it would be figuring out how to ensure there are some common patterns / procedures so folks can hop from one to another (and for those looking in to understand what to expect etc)

[dims]

examples

• https://containerd.io/releases/
• https://kubernetes.io/releases/release/
• https://github.com/dapr/community/blob/master/release-process.md

I do understand that otel has a LOT more individual pieces compared to other projects for sure, which makes it all the more desirable to have some common elements.

[austinlparker]

@dims please take a look at https://github.com/open-telemetry/community/blob/main/RELEASE.md and let me know if there's anything else you'd want to see there.

[dims]

Austin, can you please check on the links to the teams links? "Release Maintainers"

is there a link to criteria for folks aspiring to becoming one of these maintainers?

[austinlparker]

Austin, can you please check on the links to the teams links? "Release Maintainers"

is there a link to criteria for folks aspiring to becoming one of these maintainers?

The links point to the maintainers team for each repository. Are you not able to access it? Our general guidance on becoming a maintainer is defined in the membership guide at https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#maintainer.

ed: For clarity's sake, no SIG currently has different maintainers and release maintainers (there is no separate 'release team'). This is because all of our SIGs/subprojects release more or less independently in response to several events which are laid out in the table in that release file. In the future, we'll evaluate the possibility of moving to a 'wave' release that normalizes this across all repositories/artifacts.

[dims]

first 3 links for example are 404-ing for me

[austinlparker]

first 3 links for example are 404-ing for me

Hm, ok, weird. I would have thought someone in the CNCF org would be able to access those. Let me see what we can do.

[austinlparker]

What if we added a link to https://opentelemetry.io/community/members/#maintainers and told people to cross-reference that against the repo/sig...? It's not the only place to find it (conventionally, all repos should have this info in their README.md as well) but would that work for now?