Skip to content

docs: triage proposal draft#27298

Open
reggie-k wants to merge 2 commits intoargoproj:masterfrom
reggie-k:update-triage-docs
Open

docs: triage proposal draft#27298
reggie-k wants to merge 2 commits intoargoproj:masterfrom
reggie-k:update-triage-docs

Conversation

@reggie-k
Copy link
Copy Markdown
Member

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:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Title of the PR
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

Signed-off-by: reggie-k <regina.voloshin@codefresh.io>
@reggie-k reggie-k requested review from a team as code owners April 12, 2026 13:56
@bunnyshell
Copy link
Copy Markdown

bunnyshell bot commented Apr 12, 2026

✅ Preview Environment deployed on Bunnyshell

Component Endpoints
argocd https://argocd-j64dba.bunnyenv.com/
argocd-ttyd https://argocd-web-cli-j64dba.bunnyenv.com/

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

  • 🔴 /bns:stop to stop the environment
  • 🚀 /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

Signed-off-by: reggie-k <regina.voloshin@codefresh.io>
@codecov
Copy link
Copy Markdown

codecov bot commented Apr 12, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.35%. Comparing base (25e0c38) to head (d4af98c).
⚠️ Report is 3 commits behind head on master.

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.
📢 Have feedback on the report? Share it here.

* **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.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants