Provenance

The Overture Data Management System is developed using an agile development approach utilizing public Github Issues to track new features, improvements and production defects. Releases are constructed around major new features or critical bug fixes and are authorized by an internal team of stakeholders led by the Product Owner.

Each Overture DMS component identified for an upcoming release is individually tested as part of our standard development process. As the Overture DMS is comprised of multiple interconnected components, it is also tested and eventually released as a single package. Once target versions of a new release package are identified, a robust set of testing is completed to ensure that the explicit versions being included within a given release are successfully functioning together as intended. In this spirit, testing is performed on individual service components, as well as across the platform as whole, to ensure end-to-end use cases and scenarios are covered.

Each release that is made will coincide with the appropriate level of documentation updates which, depending on the nature of the release, can include updates to the DMS Installation & Configuration Guide, DMS Admin Guide, DMS User Guide, DMS Release Notes, and GitHub ReadMe.

The Overture DMS ecosystem is dependent on existing third-party packages such as Elasticsearch. The supporting team is monitoring dependency alerts and will trigger the issuing of appropriate patch releases of the DMS if any dependent third-party packages issue critical bug fixes or vulnerability updates. The patch releases triggered by this process will follow the same robust individual component and package testing process as outlined above.