-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Release Automation
Use Case
As a node engineer
I want to reuse the new driver release workflow
So that I can make kerberos changes available swiftly and securely
User Impact
- None
Dependencies
- None
Unknowns
- Do prebuilds have to be a part of the CI release?
- Reuse the driver systems, but needs some redesign for the shared repository.
- How do we want to format PR templates as to not impact other teams?
- Changelog lives in nested directory and not every commit is formatted correctly for conventional commits, can the tooling handle this?
Acceptance Criteria
Implementation Requirements
- Unknown
Testing Requirements
- Manual verification
- Use dry-run flag to test with manually kicked off release runs
- Run a release_notes test against a release PR
Documentation Requirements
- Update release instructions if any salient details are different from the driver's steps
Follow Up Requirements
- None