open-telemetry/opentelemetry-specification

Add GitHub workflow, that helps SIG maintainers to keep track of spec changes

Open

#4,073 opened on Jun 11, 2024

View on GitHub
 (5 comments) (5 reactions) (0 assignees)Makefile (987 forks)auto 404
Stalehelp wantedsig-issuespec:miscellaneous

Repository metrics

Stars
 (4,267 stars)
PR merge metrics
 (PR metrics pending)

Description

What are you trying to achieve?

See https://github.com/open-telemetry/community/issues/2087

As suggested there, I propose that we add a workflow to the spec repo that is triggered on release and raises an issue on the language SIGs with the release notes. The SIG maintainers can then handle the issue within their own triage process.

I would suggest to roll this out for 1-2 SIGs first and then add the other ones later.

I am happy to help with building that workflow, I created this issue beforehand to verify that this is what we want to do.

Contributor guide

Research direction
Review the existing GitHub Actions workflows in the repository and understand the release process. Then design a workflow that triggers on release and creates issues in designated language SIG repositories with release notes.
Tech stack
github actions
Domain
devopsci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65