andygrove opened a new pull request, #7708:
URL: https://github.com/apache/datafusion-comet/pull/7708

   ## Which issue does this PR close?
   
   N/A. The first report made with this change is #7707.
   
   ## Rationale for this change
   
   The weekly bug triage report only listed the issues triaged that week, so it 
gave no picture of the critical bugs that are still open. It was also too long 
to cover in a 30 minute meeting.
   
   ## What changes are included in this PR?
   
   Changes to the `bug-triage` skill (`.ai/skills/bug-triage/SKILL.md`) only:
   
   - The report opens with `## Open critical bugs`: a table of open critical 
bugs by area with a count of new ones, then a list per area. New issues are 
marked `**NEW**` and get a one-sentence rationale.
   - Each issue is counted under one primary area, chosen by a fixed order of 
the existing area labels, so the counts add up to the total.
   - The table compares each area with the previous report. It does so only 
when the previous report is at most 10 days old and has this table; otherwise 
the column is left out. Earlier reports have no such table, so the first report 
made with this change has no comparison.
   - The rest of the report is shorter. Escalations, skipped and failed issues 
move into one "Needs a decision" section. Medium and low bugs and all 
enhancements are a title and link in collapsed blocks. Rationale stays only for 
new critical bugs, high bugs and the decision items.
   
   ## How are these changes tested?
   
   I ran the skill against the live queue (19 issues) and it filed #7707. The 
labels, the by-area counts (26 open critical bugs, 1 new) and the layout came 
out as described. I checked that #7596, a critical bug in last week's report, 
is closed rather than missing.
   
   The week-over-week comparison has not run yet, because the previous report 
#7640 has no `## Open critical bugs` table. It will first run on the next 
report. `prettier --check` passes on the file.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to