Minnow Bug Triage: Difference between revisions
From Yocto Project
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 47: | Line 47: | ||
{{#bugzilla: | {{#bugzilla: | ||
|status=!(RESOLVED,VERIFIED,CLOSED) | |status=!(RESOLVED,VERIFIED,CLOSED) | ||
|hardware=MinnowBoard Max | |||
|severity=!janitors | |||
|columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated | |||
|sort=id | |||
|noresultsmessage="No matching bugs found." | |||
|total=summary | |||
}} | |||
== MinnowBoard-MAX Closed Bugs == | |||
{{#bugzilla: | |||
|status=(RESOLVED,VERIFIED,CLOSED) | |||
|hardware=MinnowBoard Max | |hardware=MinnowBoard Max | ||
|severity=!janitors | |severity=!janitors |
Revision as of 20:35, 14 May 2014
Goal
The output of the bug triage meeting should be that all bugs have an owner, a target milestone, and a priority.
Prior to the meeting, each Product Owner should review their Weekly New and High Bugs and be ready with any opens. An example open would be a bug that may need to change Products.
Agenda
- Opens
- Collect opens
- Discuss opens
- Review Queries
- State number and owner
- Owner makes any modifications
- Assign owner, target milestone, and priority.
Note: for Yocto Project bugs go to: Bug Triage
Bug Criteria
- Priority-Severity
- High-Critical: Two Week
- High: Milestone
- Medium: Nice to have for milestone, must have for release
MinnowBoard Bug Triage Searches
Non-Prioritized Bugs
ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
---|---|---|---|---|---|---|---|---|
0 |
MinnowBoard v1 Open Bugs
ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
---|---|---|---|---|---|---|---|---|
0 |
MinnowBoard-MAX Open Bugs
ID | Summary | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
---|---|---|---|---|---|---|---|---|
0 |
MinnowBoard-MAX Closed Bugs
ID | Summary (15 tasks) ⇒ | Severity | P | Milestone | Assignee | Status | Whiteboard | E |
---|---|---|---|---|---|---|---|---|
6185 | Alsa does not detect the audio device | major | High | --- | Darren Hart | VERIFIED | ||
6190 | Firmware doesn't autodetect and boot FS0:/EFI/BOOT/bootx64.efi | minor | Medium | Production Release | Darren Hart | VERIFIED | ||
6199 | High Speed Expansion Testing | normal | High | A1 Release | David Anders | VERIFIED | ||
6470 | Specify ACPI SPI UID=0 | normal | Medium | Production Release | Darren Hart | VERIFIED | ||
6486 | ALSA device is not detected by OS (bad VERB tables maybe?) | critical | High | Production Release | He, Tim | VERIFIED | ||
6488 | Enable Calamari LPSS devices by default | normal | Medium+ | Production Release | Darren Hart | VERIFIED | ||
7770 | Errors found on dmesg MM 32 bits firmware for core-sato-sdk image | normal | Medium | 1.9 | California Sullivan | VERIFIED | ||
7898 | Dmesg error controller can't do DEVSLP on Minnow Max | normal | Low | 1.9 | California Sullivan | VERIFIED | ||
7901 | Dmesg error failed to retrieve link info, disabling eDP on Minnow Max | normal | Low | 1.9 | California Sullivan | VERIFIED | ||
8473 | Parselogs error: Online check failed for 0xb77b2ab0 Wired on lsb image | normal | Medium | 2.1 | Saul Wold | VERIFIED | ||
8689 | Parselogs error: can't open '/dev/ttyPCH0': No such file or directory^M in lsb image | normal | Medium | 2.1 | Cristina Agurida | VERIFIED | 3 | |
9860 | LAN device doesn't retrieve connection after resume from suspend state | normal | Medium+ | 2.2 M3 | David Rodriguez | VERIFIED | ||
10262 | SD card not being recognized when trying to install the image | normal | Medium+ | 2.2 M4 | Alejandro Hernandez | VERIFIED | YP 2.2 M4 RC1 BUILD BLOCKING BUG | |
10514 | test_parselogs on genericx86-lsb minnow board max 32 FAILED LOGIN (1) on '/dev/tty1' FOR 'UNKNOWN', Authentication failure | normal | Medium | 2.3 | David Lopez Barriba | VERIFIED | possible 2.2.1 | |
12213 | [TC 1059] test_parselogs failed on MMAX64 (Turbot) with direct firmware load for rtl_nic/rtl8168g-2.fw error | normal | Medium | 2.5 | California Sullivan | VERIFIED | ||
15 |