|Release Name||Status||Release Date||Next Phase|
|Demeter Point Release 2||Planning|
|Demeter Point Release I||Requirements Def|
|Planning||Pre-M0. The release name has been chosen and tentative milestone dates have been determined.|
|Requirements Definition||Between M0 and M1. The schedule has been approved and requirements are being documented and prioritized.|
|Development||After M1 but before release. Requirements are being implemented and tested.|
|Current Release||The approved output of the release process which interested end users should be deploying. This release will be maintained until it is replaced by the next release.|
|End of Life (EOL)||This release has been replaced by a newer release and is no longer supported.|
Master Branch Release Notes
Each component has its own page of release notes which can be accessed from http://docs.acumos.org/en/latest/release-notes/index.html
Acumos provides consumable releases every six months. A release of Acumos provides an installable datacenter reference platform, providing a variety of compositions and associated functions applicable for carrier network virtualization.
Users and developers should be provided an integrated, operational data-center build derived from open source projects which has undergone a basic level of testing. This should be able to be deployed on an Acumos compliant infrastructure for the purpose of hosting applications and delivering services.
The Release Process
Acumos releases provide a method for community projects to coordinate and release their code and features in a coordinated simultaneous release.
Projects intending to participate in a release need to communicate this intent to the release project during release planning.
The release calendar and planning and status details are available below
Acumos JIRA Flow
Epic- Either it’s a new feature / improvement we will tag it as Epic to be captured in the requirements document.
Story: If any epic is run across multiple components or modules then will add multiple stories to the epic. Stories can also be broken down into SubTask.
Task: Only independent supporting requirements will be marked as task. No SubTask will be created under the task.
Sub Task: to be created only under the Story. Once all the Subtask are completed then the story will be marked as done.
Summary and details for development sprints is provided under Sprint Planning (Archived).
An Acumos release will provide an automatic and repeatable deployment and installation to a compliant configuration of servers.
Lifecycle-Managing Acumos Deployments
As the Acumos project further develops current and new components, they go thru a process of integration and system testing, as described under Weekly builds. As an adjunct to that process, the new ready-for-testing components are validated in the platform deployment tests by the OA&M project team through the system-integration repo toolsets, for Azure (k8s) and AIO (docker, generic k8s, and OpenShift k8s). Because there may be cross-component dependencies (e.g. for new versions of the CDS and database), the OA&M project ultimately releases a new version of system-integration based upon the Release Assemblies as shown at Weekly builds. That release of system-integration currently represents "User Acceptance Testing" completion.
End-users may also want to integrate/test new component versions in advance of the completion of a release assembly. The system-integration tools should enable the redeployment of individual components by users, given that the user has addressed any dependencies such as component configuration (template and external data), and cross-component dependencies. So if users want to use unreleased components (snapshot repository images), they can, but need to ensure they are aware of and have addressed any dependencies.