group queued releases in build-queue page
Open
Nobody has claimed this yet.
A-backend
A-builds
E-easy
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 232
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 60
Description
Coming from this zulip discussion.
Especially when we do rebuilds of many crates (and even more when we do #464 ) the build queue page can get quite long and probably confusing for crate authors.
One idea would be to:
- group the queue into sections by priority groups (normal prio, deprioritized, perhaps manual rebuilds, automated rebuilds)
- hide the "automated rebuilds" by default, perhaps only showing the count, with a link to show them.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The entry point is the build-queue page; start by locating how queued releases are currently rendered and read the linked Zulip discussion for context. Done means the queue is visibly grouped by priority, while automated rebuilds are collapsed by default with their count and a way to expand them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100