<div dir="ltr">Once we have a release-quality image, won't most people get the image from the Docker registry? So the name of the tarball isn't so much important as the tag, which already tracks the creation date. We'll want to have a discussion about that tagging strategy at some point, but spending too many cycles on how to name the tarballs, which should only be for testing images that aren't GA yet, seems a waste.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Apr 12, 2014 at 8:55 PM, Karanbir Singh <span dir="ltr"><<a href="mailto:mail-lists@karan.org" target="_blank">mail-lists@karan.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">On 04/12/2014 06:31 PM, Dusty Mabe wrote:<br>
> On Fri, Apr 11, 2014 at 6:31 PM, Karanbir Singh <<a href="mailto:mail-lists@karan.org">mail-lists@karan.org</a>> wrote:<br>
>><br>
>> worth noting that this is represented as CentOS-6, dropping the point<br>
>> release and replacing it with a date - means we can update it more<br>
>> frequently than only at every point release time ( and we set user<br>
>> expectation around that ). We can, if there is a need, still push images<br>
>> that are in line with a point release snapshot.<br>
><br>
> Do you think it would be beneficial to have both the point release and<br>
> the date? For example:<br>
><br>
> CentOS-6.5-20140411-x86_64-docker_01.img.tar.bz2<br>
><br>
> If you start to try to compare behavior within this image to CentOS<br>
> 6.5 installed on a normal piece of hardware it might be easier if we<br>
> can easily look at the image file name and know what point release to<br>
> compare it to.<br>
><br>
> An argument can also be made that this might spark confusion.<br>
><br>
> Thoughts?<br>
<br>
</div>There is certainly value in having GA / ISO matching images in most<br>
places as well, for those - adding the point qualifyer makes sense. But<br>
I think the default image we recommend people adopt should just be the<br>
CentOS-<Release>-<datestamp> one, also available as<br>
CentOS-<Release>-latest; So people getting onboard, get the best<br>
possible experience, and those who know what they are doing and still<br>
want a GA inline release, can get it - by jumping through a hoop or two.<br>
<br>
- KB<br>
<div class="im HOEnZb"><br>
<br>
--<br>
Karanbir Singh<br>
<a href="tel:%2B44-207-0999389" value="+442070999389">+44-207-0999389</a> | <a href="http://www.karan.org/" target="_blank">http://www.karan.org/</a> | <a href="http://twitter.com/kbsingh" target="_blank">twitter.com/kbsingh</a><br>
GnuPG Key : <a href="http://www.karan.org/publickey.asc" target="_blank">http://www.karan.org/publickey.asc</a><br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos-devel" target="_blank">http://lists.centos.org/mailman/listinfo/centos-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Chris St. Pierre
</div>