Short, honest guides to the concepts ArcRelease is built on: what they mean, how they are measured, and where the common definitions mislead.
What it covers, how it differs from CI/CD and change management, and why it breaks down.
Read more →How to calculate it, what counts as a failure, and why a checkbox measures diligence, not failure.
Read more →What a change or code freeze is, when to use one, and how to run one that people do not route around.
Read more →Hard and soft dependencies between releases, and how to see what blocks what before you ship.
Read more →What auditors ask for on change management, and how to capture it at the moment of the decision.
Read more →The glossary defines the release management terms used across these guides, each with its own link you can share or quote.
Tell us about your release process. Connect your stack in ten minutes, run a Gaja preflight on a real release, and see the reasons behind the verdict.
Free plan · ten minute setup · we reply in one to two business days