Update issue sorting process #1220
Conversation
conda-bot
added
the
cla-signed
HOW_WE_USE_GITHUB.md
Outdated
| ### When do items move out of the "Sorting" tab? | ||
|
|
||
| Items move out of the ["Sorting" tab][project-sorting] once the investigatory phase described in [What is done about the issues in the "Sorting" tab?](#what-is-done-about-the-issues-in-the-sorting-tab) has concluded and the sorting engineer has enough information to make a decision about the appropriate resolution schedule for the issue. The additional tabs in the project board that the issues can be moved to include the following: | ||
| Items move out of the ["Sorting" tab][project-sorting] once the investigatory |
There was a problem hiding this comment.
What's the change here? Just the new line, right?
I see several of these in this PR.
There was a problem hiding this comment.
Hi @ForgottenProgramme, it becomes very hard to see the diff because we should have some maximum line length setting for docs W505:
[tool.ruff.lint.pycodestyle]
max-doc-length = 88
There are changes here and in each paragraph, for example renaming sorting engineer to core maintainer.
soapy1
left a comment
soapy1
left a comment
There was a problem hiding this comment.
Nice improvements. It would also be nice to carve out some time in our sprint plans to address triaging and cleaning up issues.
| appropriate resolution schedule for the issue. The additional tabs in the | ||
| project board that the issues can be moved to include the following: | ||
|
|
||
| - **"Support"** - Any issue in the ["Support" tab of the Planning board][project-support] is a request for support and is not a feature request or a bug report. Add the https://github.com/conda/infrastructure/labels/type%3A%3Asupport label to move an issue to this tab. |
There was a problem hiding this comment.
It would be nice to have a seperate place for support type questions if possible. That way the issue tracker can just be for tracking issues and feature requests.
.github/workflows/project.yml
Outdated
| # issues are added to the conda Roadmap and Sprint Planning project | ||
| # PRs are added to the Review project | ||
| project-url: https://github.com/orgs/conda/projects/${{ github.event_name == 'issues' && 2 || 16 }} | ||
| project-url: https://github.com/orgs/conda/projects/${{ github.event_name == 'issues' && 22 || 16 }} |
There was a problem hiding this comment.
This will auto add ALL new issues to this project, is that what we want?
There was a problem hiding this comment.
A better choice for this would be to delete this workflow and to instead enable the add cards to workflow in the project itself
5 participants
Description
As one of the lessons learned from the last sprint, the team wanted to archive the Planning project board and remove the sorting process since it isn't currently being executed as is. After looking at it in more detail, I think without a sorting process there would still be an implicit way in how we triage issues and requests.
Instead of removing the process, I updated it to match how we are currently using the Roadmap and Sprint project. Although there is currently no rotating sorting engineers, there is still sorting going on, and we probably need to invest more time in it in the coming quarters.