#150: Docker container refresh cadence
----------------------------+---------------------
Reporter: acarter | Owner:
Type: task | Status: new
Priority: normal | Milestone: Future
Component: Docker (Other) | Resolution:
Keywords: meeting |
----------------------------+---------------------
Comment (by acarter):
Some pros and cons shared by MattDM:
I can think of several reasons that having a two-week cadence might be
beneficial:
* Fights the (accurate) perception that Fedora updates are an unmanageable
firehose
* If some layered images represent modules, and we want the modules to
work together, putting them in batches makes it easier to test that a
given batch _does_ work as a coherent whole
* Provides a rhythm that both users and developers can expect.
On the other hand, we NEED to be able to deliver updates out-of-cycle for
critical and important updates (both security and bugfix), and it's also
important to make other bugfixes (and new features) available to people
who want them without having to wait.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/150#comment:1>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
