Queue times to be reviewed during the July 2024 release
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
**Summary**
Downside of everyone and their dog using Grinders for all kinds of good work is that it is more difficult to spot the ones launched to complete release triage.
_Originally posted by @smlambert in https://github.com/adoptium/temurin/issues/28#issuecomment-2013303022_
Addendum by adamfarley: During the retrospective, it was proposed that we monitor the queue times during the next release to identify how severe a problem this is, where it is most severe, etc.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the Grinders used for release triage and review how queue times can be measured during a release; done means identifying where the problem is most severe and documenting the resulting findings.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100