[cloud] #59: Process for determining when and why Docker trusted images need to be rebuilt

2014-05-21 Thread Fedora Cloud Trac Tickets
#59: Process for determining when and why Docker trusted images need to be
rebuilt
+
 Reporter:  scollier|  Owner:
 Type:  task| Status:  new
 Priority:  normal  |  Milestone:  Future
Component:  Docker (Other)  |   Keywords:
+
 We have several Docker trusted images hosted on the Docker index:

 https://index.docker.io/u/fedora/

 These are built from the Fedora Cloud github account here:

 https://github.com/fedora-cloud/Fedora-Dockerfiles

 We need a clear process for deciding when these layered images need to be
 rebuilt.  Is it when new RPMs are released?  Security errata?  Changes to
 config files?  What are other criteria that could trigger the need for a
 rebuild?

-- 
Ticket URL: https://fedorahosted.org/cloud/ticket/59
cloud https://fedorahosted.org/cloud
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


Re: [cloud] #59: Process for determining when and why Docker trusted images need to be rebuilt

2014-05-21 Thread Fedora Cloud Trac Tickets
#59: Process for determining when and why Docker trusted images need to be
rebuilt
+-
 Reporter:  scollier|   Owner:
 Type:  task|  Status:  new
 Priority:  normal  |   Milestone:  Future
Component:  Docker (Other)  |  Resolution:
 Keywords:  meeting |
+-
Changes (by mattdm):

 * keywords:   = meeting


-- 
Ticket URL: https://fedorahosted.org/cloud/ticket/59#comment:2
cloud https://fedorahosted.org/cloud
Fedora Cloud Working Group Ticketing System
___
cloud mailing list
cloud@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct