-
Notifications
You must be signed in to change notification settings - Fork 2
Home
A System releases is a snapshot of the deployed system, that is, it is a snapshot of the system context of the C4 architecture model. A system release is comprised of A) the set of code released to production, B) the verification and validation that has been done at the system level, and C) the documentation and guides for using the software or platform.
Initially, system releases will be manually curated efforts every few months. The long term goal will be to automate 'system releases' and have them be a by-product of the code release and promotion to test and production envrironments.
| Version | Release | Date | Description |
|---|---|---|---|
| Unity .1 R1 | Unity .1 Prototype Release 1 | 04/15/2022 | Release 1 of the Unity Prototype... |
| Unity .1 R2 | Unity .1 Prototype Release 2 | 07/15/2022 | Release 2 of the Unity Prototype... |
| Unity .1 R3 | Unity .1 Prototype Release 3 | 09/15/2022 | Release 3 of the Unity Prototype... |
Each component of Unity (for example, the algorithm catalog) has its own set of releases. Releases can be viewed from each of the repositories within this organization. The component release happens at the container (no, not Docker container) level of the C4 architecture model. The development team is responsible for the code, unit testing, integration testing, and documentation of their component.
Architecture and Design
Architecture Diagrams, sequence diagrams, and more are available on our architecture overview page.
Requirements
Issue Management
Configuration Management
Inspiration
"[We've experienced] lots of red tape between teams - which made things difficult. I am proposing we should not do that."