Tagged articles
release-engineering
21 articles · Page 1 of 1
Meta's Astryx design system, open-sourced after eight years internally, delivers 150+ accessible React 19 components with CSS-variable theming, a swizzle CLI for source ejection, and an AI-agent evaluation suite, while its release pipeline ships hourly canaries and stable versions from immutable tags via a dual-lane GitHub Actions workflow constrained by npm's trusted publishing limits.
AI-evaluationAstryxCSS-variables
0 likes · 13 min read

The article details a continuous delivery pipeline for high-quality datasets, combining Dataset CI for contract validation and Eval CI for task regression, with automated quality gates, manual approvals, canary releases, and full-baseline rollback, using a policy knowledge base as a running example.
Agent EvaluationContinuous DeliveryDataset CI
0 likes · 29 min read

Xiaohongshu engineered a Harness system to manage agent-driven recommendation releases spanning 10+ hours across thousands of pods, using persistent tasks, declarative templates, a reconciliation engine, and effect-verified external actions to reliably execute cross-day deployments with human-in-the-loop governance.
Agentic SystemsHarnessProduction Operations
0 likes · 24 min read

This article explains why canary releases become essential at 10M QPS, detailing how to define canary units by identity, failure domain, and business scenario; set absolute traffic limits; use evidence-driven state machines with four metric layers; ensure version compatibility; choose rollback, feature-flag, or forward-fix strategies; build platform capabilities; avoid common pitfalls; and make canary the default deployment path.
10M QPSRollback StrategyVersion Compatibility
0 likes · 30 min read

This article explains why anytime deployment fails at 10M QPS scale and details a comprehensive change window mechanism that controls change quantity, risk exposure rhythm, personnel availability, and recovery resources, including layered windows, admission criteria, controlled rollout phases, freeze periods with emergency lanes, automated gates, and effectiveness metrics.
Production OperationsRisk Controlautomation gates
0 likes · 30 min read

The article explains why independent deployment doesn't guarantee independent service evolution, detailing five required capabilities—identifiable dependencies, compatible interfaces, controllable traffic routing, verifiable releases, and recoverable failures—using a refund service case study to illustrate dependency topology, interface evolution patterns, phased release strategies, and evidence-based rollback decisions.
Dependency ManagementRollback Strategycanary deployment
0 likes · 21 min read

The article explains how moving feature switches from hard‑coded if‑else statements to a platform‑based runtime system enables granular targeting, gradual rollouts, A/B experiments, instant kill‑switches, and SDK‑based local evaluation that can handle millions of queries per second without redeployments.
A/B testingKill SwitchSDK local evaluation
0 likes · 17 min read

The article explains why the last mile of software delivery—merging, testing, changelog, version bump, documentation sync, and retrospection—is often the bottleneck, and introduces three automated skills (/ship, /document-release, /retro) that institutionalize these tasks to create a closed‑loop workflow.
Continuous IntegrationGit workflowautomation
0 likes · 15 min read

This article provides a comprehensive overview of release engineering, covering branch models, naming conventions, merge processes, Git commit standards, CI/CD stage design, environment isolation, artifact management, product delivery steps, deployment strategies, and rollback procedures to ensure reliable software releases.
CI/CDKubernetesOperations
0 likes · 26 min read

The article outlines Google’s release engineering principles, roles, and processes—including self‑service, frequent high‑speed releases, sealed builds, policy enforcement, configuration management, and the Rapid system—to illustrate how automated, reliable software delivery is achieved at scale.
Configuration ManagementContinuous IntegrationSRE
0 likes · 14 min read

The paper describes Bilibili’s Caster platform, which implements standardized workflows, left‑shifted pre‑checks, tiered release checkpoints, and an emergency green‑channel to safely manage containerized application changes, providing real‑time observability, automated rollback, and capacity‑aware scaling that together cut change‑induced incidents and improve production stability.
CI/CDcloud-nativecontainer platform
0 likes · 17 min read

Tencent Cloud Object Storage (COS) boosted release efficiency and quality by evolving its architecture to YottaStore’s cluster‑percentage changes, introducing Management Zone‑based parallel upgrades, automated gray‑testing and rollbacks, streamlined concurrency controls, visualized flow‑time reductions, standardized quality checks, and a five‑level maturity model aimed at fully automated, reliable deployments.
Tencent COScloud storageoperational efficiency
0 likes · 16 min read

This article examines Facebook's mobile continuous deployment approach, detailing how increased release frequency, automated pipelines, and a clear separation between development and release engineering have allowed weekly Android and iOS updates without sacrificing software quality or developer productivity.
Facebookcontinuous deploymentmobile
0 likes · 9 min read


DevOpsOct 19, 2021 · Fundamentals
The article analyzes common reasons why defects escape testing and appear in production—ranging from missed test cases and environment differences to incomplete releases—and offers a step‑by‑step checklist of practices to improve testing, release processes, and risk mitigation.
production issuesquality assurancerelease-engineering
0 likes · 8 min read

This article explains how Facebook engineered a massive‑scale continuous delivery pipeline—evolving from manual cherry‑pick releases to a near‑continuous deployment system that safely pushes hundreds of code changes per hour to both web and mobile users worldwide.
Continuous DeliveryDevOpsFacebook
0 likes · 14 min read

This article explains how Facebook built a highly scalable continuous delivery pipeline for both web and mobile products, evolving from simple trunk‑based releases with cherry‑picks to a quasi‑continuous deployment model that supports thousands of engineers, rapid rollouts, and robust quality monitoring.
Continuous DeliveryFacebookdeployment
0 likes · 14 min read

The article explains how LinkedIn applied the 10X rule—setting ambitious, ten‑fold goals—to overhaul its mobile development process, introducing weekly releases, aggressive testing, static analysis, distributed builds, and feature‑flag‑driven deployments to dramatically improve engineering efficiency and product delivery speed.
10xCI/CDContinuous Delivery
0 likes · 14 min read

The article outlines the core duties, essential skills, and ideal candidate profile for a Build & Release Engineer, covering repository management, CI/CD pipelines, automation scripting, DevOps tool expertise, and communication abilities needed to ensure reliable software delivery.
build managementrelease-engineeringsoftware delivery
0 likes · 4 min read


21CTONov 1, 2017 · Operations
This article explains how Facebook evolved its release engineering process from manual cherry‑picking to a quasi‑continuous push‑from‑master system, enabling thousands of daily code changes, reducing hot‑patches, supporting global engineers, and improving user experience across web and mobile platforms.
Continuous DeliveryDeployment Automationfacebook engineering
0 likes · 13 min read

This article details a step‑by‑step transformation of an internet finance platform's online release process, covering application architecture, public component selection, smooth deployment techniques using Dubbo weight adjustment, RocketMQ control, LTS task isolation, verification methods, and a comprehensive gray‑release strategy with practical pitfalls and future improvements.
Gray ReleaseOperationsRocketMQ
0 likes · 16 min read


21CTOMar 22, 2016 · Operations
During an exclusive visit to Facebook’s Menlo Park campus, the author uncovers the company’s sophisticated release engineering practices—including the HipHop optimizer, a custom BitTorrent‑based deployment system, continuous testing, and a unique “Hotfix Bar” culture—revealing how billions of daily requests are reliably delivered at massive scale.
FacebookOperationsbitTorrent
0 likes · 18 min read
