Conversation
Signed-off-by: reggie-k <regina.voloshin@codefresh.io>
✅ Preview Environment deployed on Bunnyshell
See: Environment Details | Pipeline Logs Available commands (reply to this comment):
|
Signed-off-by: reggie-k <regina.voloshin@codefresh.io>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #27298 +/- ##
==========================================
- Coverage 63.40% 63.35% -0.06%
==========================================
Files 415 415
Lines 56694 56694
==========================================
- Hits 35947 35918 -29
- Misses 17367 17393 +26
- Partials 3380 3383 +3 ☔ View full report in Codecov by Sentry. |
| * **Rotation:** Triage is handled by two Argo CD maintainers rotating weekly; rotation is defined in the contributor meeting. | ||
| * **Prioritization:** Triage gives maintainers visibility into requested features and bug fixes and supports clear prioritization of new issues. | ||
|
|
||
| In discussion on the source doc, maintainers described this as a **guideline**, not rigid rules: trivial fixes and documentation-only changes are typical exceptions where strict issue-first process adds friction without much benefit. |
There was a problem hiding this comment.
I would just remove the source doc reference and start saying: "This proposal is a guideline..."
|
|
||
| New issues are managed via the | ||
| [triage GitHub project board](https://github.com/orgs/argoproj/projects/37/views/2) | ||
| by setting **Status** to one of: |
There was a problem hiding this comment.
Maybe add the user-story behind this board so ppl have clarity of the intention:
As an Argo CD maintainer, while doing triage, I want to see the list of pending triage issues sorted by creation date so I can have full visibility and can change the triage status in one click.
The idea is to establish clearer requirements for PRs and clearer DODs for triage so that the process is more effective and we can get better visibility on the issues and plan the releases better.
This aim of the proposal is to continue the discussion so that we can reach a decision and start following the guidelines accepted by the maintainers and/or further refine the guidelines.
Checklist: