Responsibilities:

Release Responsible: Responsible for the ocm library release and for setting up corresponding issues to track the releases (and patches). You can find the release process documentation here. @jakobmoellerdev will support you!

Scrum Master: Responsible for moderating, taking meeting notes and follow up tasks for our regular scrum meetings! 📝

Support Coordinator: Responsible for monitoring our slack support channels #sap-tech-ocm #sap-ext-ocm-project and github issues!

Security Responsible: Responsible for monitoring and triaging security issues as described in the OCM Security Compliance / Triage Guidelines!

Dependabot Updates: Responsible for taking care of the dependabot updates for the main repositories! ⏫

Done Criteria

• Security Triage Efforts
• Release OCM as per Release Decision according to the Plan
  • Release created for last release candidate AND follow up PRs checked (ocm-website, ocm-piper-cli, brew, ...)
  • Bump PR for release branch merged
  • Release Branch Cutoff performed
  • Bump PR for main branch merged
  • Release Candidate created for Cutoff branch
• Merged / Handled Dependabot updates for org (checked / triaged)
• Clone this issue for the next Sprint and plan a handover for the next assignee in the rotation (assign the issue to the next person on rotation)
• ocm: Update github.com/mikefarah/yq/v4 #771
• chore(deps): update module github.com/aws/smithy-go to v1.23.2 open-component-model#1208 (see comment)
• Update and unignore github.com/sigstore/sigstore in open-component-model/ocm #780
• Sprint Responsible: 51 #759 (comment)

Follow ups

• (if applicable)

Releases

• Incorrectly promoted release 0.34.0 containing issues with dependencies. Retracted 0.34.0 (chore: retract release 0.34 ocm#1709).
• Cut of release 0.35.0 once the issues are fixed. Promote of v0.35.0 will be shifted to next year because this will likely introduce regressions due to the concurrency transfer PR.

Previous #759