-
Task
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
Not Selected
-
-
This follows up on these conversations:
- https://spaces.redhat.com/spaces/StackRox/pages/661160921/How+to+handle+MintMaker+updates+during+the+release+process?focusedCommentId=664404840#comment-664404840
- https://redhat-internal.slack.com/archives/C05TS9N0S7L/p1756996368507969
We should address two concerns that I have:
- Release engineers can't currently approve and merge MintMaker PRs in StackRox themselves without having approvals from rhacs-maintainers.
- There's a lot of email traffic from GitHub that I get being part of rhacs-maintainers.
The latter one is unfortunately not just a whim, it becomes unsustainable to deal with so much email traffic daily and email filters that I tried to apply don't really help.
Whatever we decide for release engineers, we should make sure they are also not overwhelmed with email traffic caused by MintMaker.
- is related to
-
ROX-30215 Document how to handle Renovate during release
-
- Closed
-
-
ROX-29981 Describe how to handle MintMaker updates during release
-
- Closed
-
-
ROX-31317 [MintMaker] Disable auto-merges for release branches in collector/scanner repository
-
- Closed
-
- relates to
-
ROX-30592 [MintMaker] Reduce Tekton task renovation frequency
-
- To Do
-