v1.2.0 on-hardware and on-device verification checklist #179
Labels
No labels
area/ai
area/backend
area/frontend
area/infra
area/scheduler
area/wled
good-first-issue
priority/high
priority/low
priority/medium
security
type/bug
type/chore
type/ci-cd
type/docs
type/feature
type/qa
v1.0.0
v1.1.0
v1.2.0
v2.0.0
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/Iris-WLED#179
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Everything in v1.2.0 that CI can't prove, because it needs the real roofline controller, a real phone, or a power meter. Each item links the issue it verifies. Do these against production (Rhoving/iac-repo#527) once it's running, or on the dev host after it's moved to demo mode per #527 §7.
Roofline controller
state_correctedwebhook withreason: "reboot"should arrive, andiris_watchdog_corrections_total{reason="reboot"}should go up by 1.docs/photosensitivity.md.Power (#153)
psu_efficiencyif needed, and record the ratio indocs/setup.md.Phones (#154)
Needs production over HTTPS, with VAPID keys set (
python -m app.vapid_keys).unapproved_tonightalert (#149) arrives on the phone the morning of a night with an unapproved scheme.Review nudges (#149)
docs/setup.md§4 work against a real ntfy server.Tick items off with a comment noting the date, the firmware or OS version, and anything that didn't match.