<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 14, 2017 at 6:32 PM, Niels de Vos <span dir="ltr"><<a href="mailto:niels@nixpanic.net" target="_blank">niels@nixpanic.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue Mar 14 23:23:22 2017 GMT+0100, Vijay Bellur wrote:<br>
> Any update on this one? We still have 3.8 and 3.9 images in docker hub.<br>
<br>
</span>3.8 should probably stay and get updated on regular basis, 3.9 should be removed and 3.10 can get added (packages landed in the Storage SIG last week).<br>
<br><div><div class="h5"><br></div></div></blockquote><div><br></div><div><br></div><div>The current scheme does not allow multiple versions to be maintained. We now have the following containers:</div><div><br></div><div>glusterfs-client - Fedora 25 with 3.9.1</div><div>gluster-centos - centos 7.3 with 3.8.9</div><div>gluster-fedora - Fedora 24 with 3.8.4</div><div><br></div><div>We could look at moving to a model where we have distro containers for every supported gluster release. This could mean that containers named gluster-centos & gluster-fedora will always have the latest versions of gluster. Older releases would have to be named after the release version - maybe something like gluster38-centos or centos-gluster38 and these containers would have the latest of the respective release branch.</div><div><br></div><div>Thanks,</div><div>Vijay</div></div></div></div>