Document testing process for candidate releases #18

mtlynch · 2024-04-17T13:13:00Z

When we are considering updating to a new version of uStreamer, we should have a regular, defined process for testing the release in TinyPilot.

To start out, the process should include:

Reviewing uStreamer's commit history for anything that might impact TinyPilot scenarios
Running through a subset of TinyPilot's normal release QA process (we should inline it here rather than linking to Notion)
Measuring latency after the update (see https://github.com/tiny-pilot/tinypilotkvm.com/issues/1021)
Create tickets to update our website (see https://github.com/tiny-pilot/tinypilotkvm.com/issues/1070) and include it in the release announcement if the latency drops by more than 5%

Resolves #18 This change documents our process for testing `ustreamer` debian packages when we aim to update uStreamer. <a data-ca-tag href="https://codeapprove.com/pr/tiny-pilot/ustreamer-debian/20"><img src="https://codeapprove.com/external/github-tag-allbg.png" alt="Review on CodeApprove" /></a>

mtlynch mentioned this issue Apr 17, 2024

Investigation: Requirements for upgrading to uStreamer 6.0 tiny-pilot/tinypilot#1777

Closed

db39 self-assigned this Apr 17, 2024

db39 linked a pull request Apr 19, 2024 that will close this issue

Document testing process for candidate releases #20

Merged

db39 mentioned this issue Apr 19, 2024

Document testing process for candidate releases #20

Merged

db39 closed this as completed in #20 Apr 26, 2024

Provide feedback