How can the community help with PRs in triage? #6020
Replies: 2 comments 2 replies
-
For PR's, Triage means that the ticket has been assigned to an internal team member to review. Part of this review is determining the priority of actually doing the review against all of their other tickets, which might be a substantial amount for some teammates. Often times properly reviewing a PR can even be more time consuming than implementing it internally, so that has to be factored in too. IMO, the best way to move a PR along is for someone to "poke" the ticket, saying how useful it would be to include. Of course, this may ultimately lead to it being rejected faster for one reason or another too. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the comments. Many of the open Triage PRs involve processor-specific changes, which your internal team members may find more difficult or time consuming to review. You might consider either a slightly more open review process or maybe some long-lived processor-specific forks for the public community to work up PRs that are easier to review. |
Beta Was this translation helpful? Give feedback.
-
There are about 69 PR's with the Triage status, out of about 180 open PRs. Can the Ghidra development team suggest any ways for the community to help advance or resolve this status? Your
Status: Triage
text says that 'information is being gathered'. If the needed information is public, we can likely help.If triage is blocked waiting for proofs that internal projects do not fail if the PR is accepted, that's a different matter.
Beta Was this translation helpful? Give feedback.
All reactions