Design the Orchestrator Release Process

Use Case

Users need to be able to count on a stable version of Orchestrator to consume leaving them unaffected with the work proceeding ahead in the development cycle.

Scope of Work

Need to define the versioning system and what constitutes each release.

Contextual Information

Requested to allow the Nightly HA Job to start using the Orchestrator and to allow others to test with more confidence.

Acceptance Criteria

1. Determine and plan the exact steps to version the Orchestrator and its releases.
2. Define the artifacts included in a release