Template to set the workflow for any given release. The goal of the template here is to use well known and tested methods, simplify the process, and reduce any ambiguity that we can. This helps to keep the focus on the product where it belongs by taking cognitive load out of managing releases. This template should also not be seen as a final word; if someone has an objectively better method that improves this process then we should generally adopt that.
Some well known and tested methods we will adopt immediately
- Semantic Versioning http://semver.org/
- Use of semver scheme for EdgeX individual services
- Discuss further whether to version the named release (ie, Barcelona - Nexus Repositories (adopted from ONAP project)
- Snapshot repo: used for merged artifacts. After the committer has performed the code review (+2), has merged the code and the build is successful, the build artifact is within the Snapshot repo. It is expected to have multiple snapshots for a single repo per day. All artifacts have same version number.
- Staging repo: used for Release candidate. Once a day, a new clean build is automatically performed. All artifacts have same version number. The Staging artifact is used for the release testing (Testing beyond unit tests).
- Release repo: this is the place where the project team (or Linux Foundation Releng Team) stores the artifacts that are deemed stabled for being consumed by the other project teams. Each team decides when to release. It is not expected to get a new release every day. No TSC approval is required for getting a new release artifact.
- Dependencies on named release
- Barcelona for example will contain a number of individual services that can be independently released. We should manifest the particular services and corresponding version of that service that will be contained in Barcelona.