Plan the first coordinated suite release
This commit is contained in:
@@ -183,10 +183,16 @@ application-role releases in one source repository.
|
||||
|
||||
- Development dependency manifests may temporarily refer to branches or
|
||||
commits while the roles are changing rapidly.
|
||||
- The projects' public repositories beneath
|
||||
`https://gitea.maximumdirect.net/eric/` are the authoritative release
|
||||
sources. Standalone roles are published through immutable Git tags.
|
||||
- Every released dependency manifest must pin each Git-hosted role dependency
|
||||
to an immutable role release tag.
|
||||
- The collection release is the compatibility record for the exact set of
|
||||
application-role versions it composes.
|
||||
- A collection release consists of its immutable repository tag, matching
|
||||
Gitea release, and the `ansible-galaxy collection build` archive produced
|
||||
from that tagged tree and attached to the Gitea release.
|
||||
- Collection integration tests must install and exercise the same pinned role
|
||||
combination delivered to consumers, starting from an environment in which
|
||||
the dependencies are not already installed.
|
||||
|
||||
Reference in New Issue
Block a user