Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release QA: Orbit 1.39.1 #26320

Open
xpkoala opened this issue Feb 13, 2025 · 0 comments
Open

Release QA: Orbit 1.39.1 #26320

xpkoala opened this issue Feb 13, 2025 · 0 comments
Assignees
Labels
#g-mdm MDM product group #g-orchestration Orchestration product group #g-software Software product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook.

Comments

@xpkoala
Copy link
Contributor

xpkoala commented Feb 13, 2025

fleetd agent:

Includes updates to:

  • Orbit: True
  • Desktop: False
  • Chrome extension: False

List versions changes for any component updates below:

  • Orbit v1.39.0 > v1.39.1
  • Desktop v1.39.0 > v1.39.1

Prerequisites

  1. Build a new fleetd from the release candidate branch as neded for Orbit, Desktop, and Chrome Extension.
Test nameStep instructionsExpected resultpass/fail
$Name{what a tester should do}{what a tester should see when they do that}pass/fail
`fleetd` local testing 1. Following [Testing TUF]([url](https://github.com/fleetdm/fleet/blob/main/tools/tuf/test/README.md)) instructions create binaries for Mac, Windows, and Ubuntu using your local TUF repository and install on macOS, Linux, and Windows hosts.
1. Confirm the hosts install with the updated version and are working correctly.
2. Confirm any new features and/or bug fixes associated with this release are working as intended.
pass
`fleetd` auto-update tests 1. Conduct the [`fleetd` auto-update n+1 test]([url](https://github.com/fleetdm/fleet/blob/main/tools/tuf/test/Fleetd-auto-update-test-guide.md))
2. QA certifies new release by commenting in issue.
3. Engineer waits at least 1 business day, then promotes update to `stable`.
1. Agent successfully auto-updates.
2. Issue is certified by QA.
3. Agent is promoted to `stable`.
4. Confirms agents running on `stable` receive the new update.
pass
`fleetd` tests 1. Set up a host in your instance to receive updates from the `edge` channels.
2. Work with engineer leading the release to push changes to the `edge` channel.
1. Confirm the hosts running on the edge channel receive the update and are working correctly.
2. Confirm any new features and/or bug fixes associated with this release are working as intended.
pass

Notes

Issues found new to this version:

Issues found that reproduce in last stable version:

What has not been tested:

  • We are not waiting the full 24 hours on edge before promoting to stable. We confirmed that this is acceptable to release this patch.

Include any notes on whether issues should block release or not as needed:

@xpkoala xpkoala added #g-mdm MDM product group #g-orchestration Orchestration product group labels Feb 13, 2025
@xpkoala xpkoala added #g-software Software product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. labels Feb 13, 2025
@jmwatts jmwatts changed the title Release QA: Orbit 1.39.0 Release QA: Orbit 1.39.1 Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#g-mdm MDM product group #g-orchestration Orchestration product group #g-software Software product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook.
Projects
None yet
Development

No branches or pull requests

3 participants