Skip to content

Commit 1e7867f

Browse files
authored
Update release tracking issue to match the actual release docs (#14250)
The release tracking issue is a bit misleading, as not all actions are actually performed by the collector release manager. And some actions don't really reflect the release docs. This splits the core/contrib/releases releases per their respective managers. I've also updated the "like" issue to a more recent one.
1 parent 081f450 commit 1e7867f

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

.github/workflows/scripts/release-create-tracking-issue.sh

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,15 +18,21 @@ if [ "${EXISTING_ISSUE}" != "" ]; then
1818
exit 0
1919
fi
2020

21-
gh issue create -a "${GITHUB_ACTOR}" --repo "${REPO}" --label release --title "Release ${RELEASE_VERSION}" --body "Like #4522, but for ${RELEASE_VERSION}
21+
gh issue create -a "${GITHUB_ACTOR}" --repo "${REPO}" --label release --title "Release ${RELEASE_VERSION}" --body "Like #14236, but for ${RELEASE_VERSION}
2222
**Performed by collector release manager**
2323
2424
- [ ] Prepare core release ${RELEASE_VERSION}
2525
- [ ] Tag and release core ${RELEASE_VERSION}
26+
27+
**Performed by collector contrib release manager**
28+
2629
- [ ] Prepare contrib release v${CANDIDATE_BETA}
2730
- [ ] Tag and release contrib v${CANDIDATE_BETA}
28-
- [ ] Prepare otelcol-releases v${CANDIDATE_BETA}
29-
- [ ] Release binaries and container images v${CANDIDATE_BETA}
31+
32+
**Performed by collector releases release manager**
33+
34+
- [ ] Prepare otelcol containers images release v${CANDIDATE_BETA}
35+
- [ ] Tag and otelcol containers images release v${CANDIDATE_BETA}
3036
3137
**Performed by operator maintainers**
3238

0 commit comments

Comments
 (0)