# Release Management Published articles for Release Management. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Zephyr in Practice: From Bare-Metal Development to Release Management DevFeed: [Zephyr in Practice: From Bare-Metal Development to Release Management]() Original publisher: [Read original article]() Author: Zephyr Project Published: 2026-08-25T05:00:55Z Content type: article Language: en Sources: [Zephyr Project]() Topics: [Zephyr RTOS](), [Embedded Systems](), [Embedded Software Dev](), [releases](), [Tooling](), [Open Source]() Tags: [2026](), [blog](), [development](), [embedded](), [embedded-systems](), [events](), [industry-conference](), [open-source](), [release-management](), [releases](), [zephyr]() ### AI overview A post-event report from Open Source Summit India 2026 examines two Zephyr sessions: adopting Zephyr from bare-metal development and maintaining downstream Zephyr releases while keeping pace with upstream development. ### Source excerpt The Zephyr community came together at Open Source Summit India 2026 in Mumbai to share knowledge and explore developments, tooling, and real-world applications across embedded systems. In this first post-event blog, we highlight two sessions from the Zephyr track. One explored why Zephyr can initially feel overwhelming to bare-metal developers, while the other examined how downstream Zephyr releases can keep pace with upstream development. ## Blue Green and Canary Deployments Explained DevFeed: [Blue Green and Canary Deployments Explained]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-08-09T16:30:08Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [Deployment](), [Software](), [Database]() Tags: [argo-rollouts](), [automation](), [blue-green-and-canary-deployments](), [ci-cd](), [ci-cd-pipeline](), [cloud](), [database](), [deployment](), [deployment-strategies](), [devops](), [dora-change-failure-rate](), [expand-and-contract-migration](), [feature-flags](), [guide](), [kubernetes](), [progressive-delivery](), [release-management](), [rollback](), [rolling-update](), [schema](), [sre](), [traffic-splitting](), [zero-downtime-deployment]() ### AI overview This guide explains blue-green and canary deployment strategies for replacing running software versions. It emphasizes that effective rollback depends on detecting problems with reliable metrics and that database schema changes can limit reversibility. ### Source excerpt Both strategies buy you the same thing, which is a cheap way to be wrong. The mechanism is the easy part, and the two hard parts are noticing you are wrong and dealing with the database. ## Software Release Management: A Practical Guide in 2026 DevFeed: [Software Release Management: A Practical Guide in 2026]() Original publisher: [Read original article]() Author: Eric Minick Published: 2026-07-20T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [Software](), [releases](), [Development](), [Deployment](), [Testing](), [CI/CD](), [feature flags]() Tags: [best-practices](), [ci-cd](), [deployment](), [feature-flags](), [guide](), [pipelines](), [release](), [release-management](), [rollback](), [software]() ### AI overview A practical guide to software release management, covering how code moves through testing, approval, deployment, monitoring, verification, and rollback. It explains the distinction between deployment and release and discusses feature flags, automated safety gates, and progressive delivery. ### Source excerpt Master software release management best practices. Learn how to reduce risk, speed up release pipelines, and ship faster with confidence in 2026. | Blog ## Unfold's Modern Mobile Release Process and the Subtle Art of Making Them Boring DevFeed: [Unfold's Modern Mobile Release Process and the Subtle Art of Making Them Boring]() Original publisher: [Read original article]() Author: Alan Cooke Published: 2024-07-12T21:40:00Z Content type: article Language: en Sources: [Squarespace](), [Squarespace Engineering Blog]() Topics: [Mobile](), [Release Management](), [Android](), [iOS]() Tags: [android](), [ios](), [mobile](), [release](), [release-management](), [release-notes](), [slack]() ### AI overview This article explains how Unfold at Squarespace changed its mobile release process from ad hoc, cumbersome releases to weekly release trains for Android and iOS. It describes shared release-captain responsibilities, limited manual intervention, Slack coordination, and remaining tasks such as checking translations and updating release notes. ### Source excerpt On the Unfold team at Squarespace, our mobile releases don't require much in the way of manual intervention or human oversight. In fact, we don't have to give releases much thought at all. But, this was not always true. This post is a look into what these non-eventful mobile releases are like, dig into how much more eventful they used to be, and walk through the work it took us to get here. ## Jane Street's Iron Style of Software Development DevFeed: [Jane Street's Iron Style of Software Development]() Original publisher: [Read original article]() Author: Yaron Minsky Published: 2017-08-24T00:00:00Z Content type: opinion Language: en Sources: [Jane Street]() Topics: [Development](), [Code review](), [Release Management](), [engineering-culture](), [Agile]() Tags: [agile](), [code-review](), [culture](), [development](), [release-management](), [tests]() ### AI overview The article describes Jane Street's "Iron style" of software development, shaped by its code review and release management tools. The approach combines pervasive expect tests, small changes, and fast review turnaround, while emphasizing that effective development practices depend on technology, problems, and organizational culture. ### Source excerpt People seem to enjoy talking about programming methodologies. They give them cute names, like eXtreme programming, Agile, and Scrum; run conferences and build communities around them; write books that describe how to use them in excruciating detail; and manifestos that lay out their philosophy.