THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Publication Schedule
Snapshots
- how do we publish the snapshots, what's the frequency?
- automatic, when HEAD is built, nightly similar to maven snapshots, or manually?
- when and how do we cleanup the snapshot images:
- when you publish an image you have a new version/hash and still can use any previous versions. They take space and will count towards a quota. We need to clean them up periodically:
- make it part of the publish job to look and delete the versions that are more than X days (or versions) old?
- when you publish an image you have a new version/hash and still can use any previous versions. They take space and will count towards a quota. We need to clean them up periodically:
Release Images
- how How should we build and publish the images for release versions of Beam?
- Start with manually, as part of Beam release;
- or by automatically triggering a job at some step of the release?
- , and automate it later.
- Should should it be a blocker for the release?
- should Should we make it part of the release and not mark release as complete until the images are published?
- For first three release(v2.16 ~ v2.18), we can make it optional, and if all these release go well, we can make it mandatory part of the release(from v2.19).
- should Should it be done by the same release owner?
- Yes, this document provides step by step guide about building, testing and pushing. In future, we can automate this process.
- should Should the validation be part of the release validation?
- Yes.
- should Should we make it part of the release and not mark release as complete until the images are published?
...