Rationale
Details on the history and discussions that led to this process can be found at Release Versioning Strategy.
Benefits
- No unexpected build failures due to upstream SNAPSHOT changes
- No need for cross-project consolidated “mega builds” to check dependency issues
- Avoids issues with trying to synchronize artifact version numbers across projects
- Improved dev and build cycle time
...
Overview
- No cross-project SNAPSHOT dependencies
- Teams to version and release on own schedule
- Source control central artifact version manifest
- Teams to declare the “correct version” for cross-project use
- Manifests located in integration repo: https://git.onap.org/integration/tree/versions/
- TSC to approve version manifest for simultaneous release, e.g. Amsterdam
- Maven plugin to warn against outdated dependencies vs. the manifest
Benefits
- No unexpected build failures due to upstream SNAPSHOT changes
- No need for cross-project consolidated “mega builds” to check dependency issues
- Avoids issues with trying to synchronize artifact version numbers across projects
- Improved dev and build cycle time
Rationale
Details on the history and discussions that led to this process can be found at Release Versioning Strategy.
Java (Maven) Artifacts Release Process
...