Skip to main content

2 posts tagged with "Release Management"

View All Tags
systemd-sysext: Test Your Immutable Image Without Breaking It

systemd-sysext: Test Your Immutable Image Without Breaking It

· 5 min read
Markus Burri
Senior Software Engineer & Architect

Many systems ship as immutable, verity-protected release images with a read-only /usr. Installing packages for testing or debugging on the target is not an option, yet test environments should stay as close as possible to the release image while temporarily adding tooling such as OpenSSH, tracing or diagnostics.

The question is therefore not "how to install software," but "how to extend the system without changing the baseline." This article shows how systemd-sysext solves this, using an OpenSSH server as the example.

Release Management in Azure DevOps: A Comparison of Options, Common Anti-Patterns, and Practical Combinations

Release Management in Azure DevOps: A Comparison of Options, Common Anti-Patterns, and Practical Combinations

· 15 min read
Vanesco Böhm
Software Engineer

Azure DevOps has no built-in Release work item type — and the gap has at least six different solutions, each borrowed from a feature built for something else.

Every team shipping software eventually needs to answer the same questions: which stories are going into Release 2.5? Which might slip to 2.6? Can a story belong to both? Who can see this during sprint planning, and who can report on it afterward? The answer depends entirely on which mechanism you reach for — and the trade-offs between them are real and non-obvious.

This article walks through each option using a consistent example: a development team preparing Release 2.5, with a handful of stories that might partially deliver in 2.5 and complete in 2.6, and a product owner who needs release membership visible during sprint reviews and in progress reports.