[atomic-wg] Issue #229 `decide on version scheme and image naming scheme for
f26`
by Dusty Mabe
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
We are now *releasing* OSTree content every two weeks rather than every night ([link](http://www.projectatomic.io/blog/2017/02/matching-fedora-ostree-released-content-with-each-2week-atomic-release/)). Next we would like to make the image names that get produced reflect in some way the OSTree content that is baked into the image. During recent development @jlebon actually suggested that we use date based versions for Fedora Atomic Host: something like `version: 20170130.0`, `version: 20170130.1`, `version: 20170215.0`, etc...
Let's decide on what we want the versioning scheme to look like and also what the image names "could look like" as a result of this.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/229
4 years
[atomic-wg] Issue #246 `Period of fedimg downtime`
by Dusty Mabe
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
There appears to be a period of downtime where fedimg was not uploading AMIs
Fedora-Atomic-25-20170226.0.x86_64 EC2 (us-west-2) ami-5051d230 hvm gp2
Fedora-Atomic-25-20170304.0.x86_64 EC2 (ap-northeast-1) ami-8cb2e5eb hvm gp2
Attached is a run of [get_ami.py](https://pagure.io/fedora-websites/blob/master/f/tools/get_ami.py) which shows a gap.
Can someone investigate why this happened?
<!!image>
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/246
4 years
