On Thu, Feb 25, 2016 at 05:54:20PM +0530, Sankarshan Mukhopadhyay wrote: > <https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service#Content_Tracking.2C_Automatic_Rebuilds> > mentions "But we don't want to block having the basic build service in > place on that; initially, updates will need to be initiated by the > container packager." > > This begets 2 questions - (a) what is the means to identify the images > which have gone stale because packagers have not updated (b) how to > packagers receive notifications that the images would need to be > rebuilt Good question. I think I wrote the sentence you're quoting, so I guess I have some responsibility to answer. :) And, I think the answer is: anything that we work on here should be lightweight, and any significant work should instead go to the system for automatic rebuilds. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
