...
Do we actually need all those tags. Having for example policy-common-alpine:2.0.0-STAGING-latest or policy-common-alpine: 2.0.0-20190925094447 tags is self-explanatory and would not be confused for the released version; only policy-common-alpine:2.0.0 might create confusion. So besides documenting these images, do we still need to push this tag during development cycle, or can we simply remove it?
Input from the PTL meeting 3 Oct 2019:
- only the release jobs should produce the release tag
- discussion if this will impact the oom charts in any way: oom charts always point to the release tag, but is it the last finalized release or the future (in development) release?
| Project | Status | Tracked by |
|---|---|---|
| ci-management | The patches that add the global templates are merged. Only calls to these templates will be needed from now on for each project | CIMAN-217 |
| policy | Base and common images are now multiarch. The patches for the rest of the images are in review. | POLICY-1997 |
...