On Fri, Sep 30, 2016 at 10:07 AM, Dusty Mabe <dusty@xxxxxxxxxxxxx> wrote: > > > On 09/29/2016 06:03 PM, Adam Miller wrote: >> Hello all, >> I was recently discussing some items around docker layered image >> release process in the future with Randy (bowlofeggs) and Patrick >> (puiterwijk). As a side effect of our discussion there were two >> questions I wanted to ask of the Cloud WG: >> >> 1) Do we want to maintain docker images for every Fedora Release or do >> we want to focus only on latest? (i.e. - do we want to maintain them >> like we do rpms or take a different position) > > Just a quick question about "ownership". In the current landscape rpm > maintainers own the packages and manage when they get updated. Would > we not have the same kind of spread out ownership for docker images? > That is the current plan, but if we like we can establish a Layered Image SIG who would be the owner of all things Layered Images and then anyone could update/fix/whatever any of the layered images. Afaik this is similar to how various programming language stack SIGs are setup. -AdamM > Dusty > >> >> 2) Do we want to keep around multiple versions of a container? >> >> For example: >> If we had the following images: >> >> registry.fedoraproject.org/cockpit:0.95-1.23 >> registry.fedoraproject.org/cockpit:0.95-1.24 >> registry.fedoraproject.org/cockpit:0.95-1.25 >> >> One we release to stable 0.95-1.25, can we delete -1.24 and/or >> -1.23? What kind of retention do we want here? (Note that rpm content >> does not currently maintain a N and N-1 in the repositories) >> >> Thank you, >> -AdamM >> _______________________________________________ >> cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx >> To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx >> > _______________________________________________ > cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
