#150: Docker container refresh cadence
----------------------------+---------------------
Reporter: acarter | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Docker (Other) | Keywords: meeting
----------------------------+---------------------
I need to get a decision from this group about what refresh cadence we
should target for docker containers. We've gotten proposals to refresh
images based on updates passing testing and moving to stable in bodhi,
based on a regularly scheduled & predictable 2 week release cycle
(alternating weeks with Atomic) and (of course) both. We need clear
guidance on what the requirement will be at F25 so that we can design
tooling to support it. If someone has an idea of what the likely
requirements after F25 will be that might help us make somewhat informed
design decisions also. We plan to create an automated build -> test ->
release workflow for these refreshes so that we can scale to a large set
of images quickly.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/150>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
