Release smoke test: clean-VM checklist per supported distro

mysticalsoap commented

2026-08-30 12:23:21 -04:00

Owner

Feature validation happens on the dev host - the realness (real routing table, DCO, resolved, Plasma) is the point. What that can never catch is the environment bug class: missing packaging deps, polkit/systemd path differences, resolvconf-instead-of-resolved DNS (dns_manager branches on it), iptables-legacy vs nft, older PyQt5.

Define a smoke-test checklist and run it in a clean VM before tagging a release:

fresh install from the packaging artifact (PKGBUILD now; Debian/Ubuntu once #44 exists)
service enables and starts; polkit authorizes a local session
import one provider
one OpenVPN connect, one WireGuard connect, one double hop
bypass on + one bypassed app resolves and egresses outside the tunnel
firewall on: no connectivity outside the tunnel when the VPN drops
disconnect: no route residue (ip route show proto 111 empty), devices gone

Arch is the only target today; Debian/Ubuntu join when #44 lands. Part of the 1.0 opening-up surface (#188) - a release should mean the checklist passed, not that it worked on the dev box.

Feature validation happens on the dev host - the realness (real routing table, DCO, resolved, Plasma) is the point. What that can never catch is the environment bug class: missing packaging deps, polkit/systemd path differences, resolvconf-instead-of-resolved DNS (dns_manager branches on it), iptables-legacy vs nft, older PyQt5. Define a smoke-test checklist and run it in a clean VM before tagging a release: - fresh install from the packaging artifact (PKGBUILD now; Debian/Ubuntu once #44 exists) - service enables and starts; polkit authorizes a local session - import one provider - one OpenVPN connect, one WireGuard connect, one double hop - bypass on + one bypassed app resolves and egresses outside the tunnel - firewall on: no connectivity outside the tunnel when the VPN drops - disconnect: no route residue (`ip route show proto 111` empty), devices gone Arch is the only target today; Debian/Ubuntu join when #44 lands. Part of the 1.0 opening-up surface (#188) - a release should mean the checklist passed, not that it worked on the dev box.

mysticalsoap added the

testing

label

2026-08-30 12:23:21 -04:00

mysticalsoap referenced this issue

2026-08-30 12:23:28 -04:00

Need to investigate the firewall/killswitch feature #87

Rows
Columns

Release smoke test: clean-VM checklist per supported distro #213