A release is the product decision to make functionality available to users. Deployment places code on production infrastructure; release determines whether users can access it. Separating the two avoids turning a feature bug into a frantic infrastructure rollback. section 13.3.4
A feature flag separates shipping code from exposing functionality. Keep a new feature disabled after deployment, then enable it for selected testers or accounts. This dark launch lets the code run in production while remaining concealed from the general user base. section 13.3.4
An enterprise discount, waiting backstage
A runtime flag chooses between new enterprise-discount logic and the legacy calculation. Deploy with the flag off; enable it for internal QA, then flip the dashboard switch when the feature is ready to launch. section 13.3.4
Figure 13.4 Separation of Concerns: Deployment is the technical operation of placing files on a server; Release is the business decision to expose those files to your users.

Compare the engineering act of placing files on a server with the product decision to expose them to users. section 13.3.4




