Software release lifecycle
A software release lifecycle is the recurring set of activities for preparing, validating, and making software versions available, together with the cycle between successive releases.
Machine Learning System Design
A release cycle is the recurring process and timing by which changes to a software system are prepared, verified, and deployed.
- How it is used
- Guides ML teams through validating, reviewing, and deploying model changes within a recurring software release process.
- How deep it goes
- Explains testing complexity, regression tradeoffs, review roles, and conditional automation without detailing a complete deployment procedure.
- Examples
- Uses a 100-sample regression scenario and an autocomplete feature that mimics an author's writing style.
- What you can do after
- Evaluate model improvements against regressions and decide when human review or automatic release is appropriate.
Read how Machine Learning System Design explains software release lifecycle →
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
A release process is a sequence of checks and distribution steps that certifies a software change for consumer use.
- How it is used
- Certifies updated infrastructure modules for consumer teams before they adopt them.
- How deep it goes
- Details testing, isolation, version tagging, documentation, and packaging, while deferring continuous-delivery implementation to a separate listing.
- Examples
- Uses a database module storing passwords in a secrets manager, tested by another team and tagged v2.0.0.
- What you can do after
- Operate/configure a module release by testing changes, tagging versions, updating documentation, and publishing artifacts.
Related concepts
- GitHub releaseuses · A GitHub release is a published repository version associated with a Git tag and optionally accompanied by release notes and downloadable assets.
- semantic versioninguses · Semantic Versioning is a version-numbering convention using MAJOR.MINOR.PATCH components to communicate compatibility impact: major for incompatible changes, minor for compatible additions, and patch for compatible fixes.
- lifecyclekind of · A lifecycle is the sequence of stages or states an entity, process, or artifact passes through during its existence.
- testused by · A test is a procedure or check that evaluates behavior using specified inputs or evidence against expected results or criteria.
- documentationhas part · Documentation is recorded explanatory, instructional, or reference information that describes a subject, system, or process to support its understanding, use, or maintenance.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.