#19 Bodhi Container Update Policy
Closed 5 years ago by cverna. Opened 5 years ago by cverna.

We should draft a proposal to FESCO to change the policy off a container update.

Karma : Do we want to require Karma ?
Days in Testing : Do we want to require X days in testing ?


Looking on this from perspective of packaging bunch of inter-dependent containers(OpenShift Origin ones). We need to have a way how to create batched updates and how to push some of the images ASAP in to the "buildroot", ideally with some automated smoke testing/CI.

If we can't have that atm, I would propose to set time in testing for 1 day or less and with no negative karma to auto-push in to stable.

In general I believe that the autopush feature is most useful, so it would be great to have it on by default even if we will have other time/karma requirements.

Looking on this from perspective of packaging bunch of inter-dependent containers(OpenShift Origin ones). We need to have a way how to create batched updates and how to push some of the images ASAP in to the "buildroot", ideally with some automated smoke testing/CI.
If we can't have that atm, I would propose to set time in testing for 1 day or less and with no negative karma to auto-push in to stable.
In general I believe that the autopush feature is most useful, so it would be great to have it on by default even if we will have other time/karma requirements.

I am +1 with that

+1

We should however put batched updates gating on the infra roadmap

Metadata Update from @cverna:
- Issue untagged with: meeting

5 years ago

Metadata Update from @jcajka:
- Issue assigned to jcajka

5 years ago

I have opened https://pagure.io/fesco/issue/2049 for the fesco to approve this change so it can get implemented.

Metadata Update from @cverna:
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata