Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out and document the process for dealing with owned-repo PRs (existing and new) #502

Closed
rgraber opened this issue Nov 15, 2023 · 2 comments
Labels

Comments

@rgraber
Copy link
Contributor

rgraber commented Nov 15, 2023

Ned has generated a list of open PRs against arch-bom-owned repos here: https://nedbat.github.io/exopublish/exo-people-60.html#team-2u-arch-bom. For each PR, we should categorize it as MERGE, CLOSE, or GROOM. The list of PRs to merge/close should be sent to Ned as there are some intermediate steps required. PRs that require more attention/grooming should be added to the arch-bom board for prioritization and grooming.

@rgraber rgraber added this to Arch-BOM Nov 15, 2023
@rgraber rgraber converted this from a draft issue Nov 15, 2023
@rgraber rgraber moved this to On-Call in Arch-BOM Nov 16, 2023
@rgraber rgraber moved this from On-Call to In Progress in Arch-BOM Nov 17, 2023
@rgraber rgraber self-assigned this Nov 17, 2023
@rgraber
Copy link
Contributor Author

rgraber commented Nov 20, 2023

@rgraber rgraber moved this from In Progress to On-Call in Arch-BOM Nov 20, 2023
@rgraber rgraber removed their assignment Nov 20, 2023
@jristau1984 jristau1984 removed the status in Arch-BOM Jul 1, 2024
@jristau1984 jristau1984 moved this to Backlog in Arch-BOM Jul 1, 2024
@jristau1984 jristau1984 changed the title Triage backlog of PRs Figure out and document the process for dealing with owned-repo PRs (existing and new) Aug 13, 2024
@robrap
Copy link
Contributor

robrap commented Oct 4, 2024

Marking this as closed. This is outdated, and docs have been updated here: https://2u-internal.atlassian.net/wiki/spaces/AT/pages/edit-v2/16387065#PR-Triage%2FReview. Additionally, it is somewhat replaced by #816.

@robrap robrap closed this as not planned Won't fix, can't repro, duplicate, stale Oct 4, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in Arch-BOM Oct 4, 2024
@jristau1984 jristau1984 moved this from Done to Done - Long Term Storage in Arch-BOM Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done - Long Term Storage
Development

No branches or pull requests

3 participants