On Thu, Aug 18, 2016 at 12:19 PM, Jason Brooks <jbrooks(a)redhat.com> wrote:
On Thu, Aug 18, 2016 at 9:35 AM, Adam Miller
> Hello all,
> This is a proposal for implementing a solution for releng ticket #6313
> Currently the compose (pungi) produces an Atomic ostree, installable ISO, and
> various cloud images nightly. Those artifacts are then tested via AutoCloud.
> I'm proposing that we add a second "new" repo, every two weeks we will
> the latest commit from the current repo/ref that has passed testing in
> AutoCloud then using the corresponding compose, reproduce the ISO and various
> cloud images using the exact same content but pointing to the new remote ref
> (which we will call fedora-atomic/24/x86_64/stable/docker-host) that is
> only updated every two-weeks. This would be added to the current two-week
> atomic release script instead of impacting pungi or other current processes.
This sounds good to me. Would this two-week repo become the default
repo on the images, and you'd rebase to the continuous one if that's
what you wanted, or would it be the other way around?
New Two-Week repo would be default and we'd document how to switch to
the continuously updated repo that comes out of bodhi for users who
would like that option. The current compose repos would then become
both the thing that is tested in AutoCloud as an unit and the origin
of content that lands in the Two-Week repo.
>> We then will add documentation for users who want to switch between release
>> streams via different repos/refs, either nightly updates.
>> The main concerns are:
>> - We would need to manage the versioning of the ref that gets synced over
>> ourselves but I think we can just version it as the compose id for
>> - Need to figure out how to extract the ostree repo/ref commit from AutoCloud
>> to ensure we're getting the right thing. This should be predictable though
>> since the artifacts are built from an ostree created in the compose.
>>  - https://fedorahosted.org/rel-eng/ticket/6313
>> rel-eng mailing list