<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 6, 2016 at 10:07 PM, Troy Dawson <span dir="ltr"><<a href="mailto:tdawson@redhat.com" target="_blank">tdawson@redhat.com</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 Wed, Oct 5, 2016 at 9:06 AM, Mohammed Ahmed <<a href="mailto:moahmed@redhat.com">moahmed@redhat.com</a>> wrote:<br>
><br>
><br>
> On Mon, Oct 3, 2016 at 8:42 PM, Troy Dawson <<a href="mailto:tdawson@redhat.com">tdawson@redhat.com</a>> wrote:<br>
>><br>
>> On Mon, Oct 3, 2016 at 7:12 AM, Karanbir Singh <<a href="mailto:mail-lists@karan.org">mail-lists@karan.org</a>><br>
>> wrote:<br>
>> > On 30/09/16 12:22, Mohammed Ahmed wrote:<br>
>> >> Even if there aren't any updates to 1.2 containers on toe repos, its<br>
>> >> still possible the containers might get rebuilt from other triggers,<br>
>> >> such as base image rebuilds and so on.<br>
>> >><br>
>> ><br>
>> > is there a precidence here ? have there been updates to a prev release ?<br>
>> > I guess the way the Dockerfile.CentOS went into 1.2 would potentially<br>
>> > constitute a change in pre-code, since Master/ at the time was already<br>
>> > 1.3Alpha, but is there another example for say a bugfix or a security<br>
>> > update ?<br>
>> ><br>
>> > Another way to look at this might be - is there a LTS like model in<br>
>> > openshift origin ?<br>
>> ><br>
>><br>
>> Nope<br>
>><br>
>> This brings up a very good point I hadn't even thought about.<br>
>> We're trying to treat a rotating product (designed to only use the<br>
>> latest version) in an enterprise / LTS way.<br>
>><br>
>> At the moment, I don't have anything else to say, as I said, I hadn't<br>
>> even thought about it until now.<br>
>><br>
>> Troy<br>
><br>
</span><span class="">> So how do we want to proceed with this. Build only the latest containers by<br>
> updating branch in container-index every time there is a release, or<br>
> do we want to update the dockerfiles to use more specific rpms by version<br>
> (will require maintenance of the rpms). In the case of latter we might<br>
> need LTS.<br>
><br>
<br>
</span>We talked about this during our Paas SIG meeting. We have decided to<br>
follow the upstream support model, which is to only support the latest<br>
release. So we will only build 1.3 images and not worry about the 1.2<br>
images. <br></blockquote><div><br></div><div>Sounds good. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have created a support page for OpenShift Origin on CentOS.<br>
<a href="https://wiki.centos.org/SpecialInterestGroup/PaaS/OpenShift-Origin-Support" rel="noreferrer" target="_blank">https://wiki.centos.org/<wbr>SpecialInterestGroup/PaaS/<wbr>OpenShift-Origin-Support</a><br>
<br>
On a related subject, once we get the rpm build automation in place<br>
(both in upstream origin spec/tito code, as well as the CentOS<br>
testing/build infrastructure) we do have an paas7-openshift-future tag<br>
that we can use to build and push beta's and release candidates.<br>
So, while we won't be supporting older releases, we can hopefully<br>
become a place that people can test/use the latest and greatest. (even<br>
if it's not stable)<br>
<div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div>So this should leave one last doubt. Do we tag the containers coming from the origin repo, with only the version tag as</div><div>we currently are or tag them as latest or both (version tag and latest tag).</div><div><br></div><div>Once the infra is in place, we should also consider how we are going the tag those containers as well.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
Troy<br>
______________________________<wbr>_________________<br>
CentOS-devel mailing list<br>
<a href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/centos-devel" rel="noreferrer" target="_blank">https://lists.centos.org/<wbr>mailman/listinfo/centos-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b>Mohammed Zeeshan Ahmed</b></div><div>Associate Software Engineer, <span style="font-size:12.8px">Redhat Developers Team (Devtools)</span></div><div><a href="http://mohammedzee1000.wordpress.com" target="_blank">http://mohammedzee1000.wordpress.com</a></div><div><br></div><div><p dir="ltr" style="margin:0px;padding:0px;border:0px;font-size:14px;font-family:"Helvetica Neue",Helvetica,Arial,"Lucida Grande",sans-serif;vertical-align:baseline;color:rgb(61,61,61);line-height:21px"><span style="margin:0px;padding:0px;border:0px;font-weight:bold;font-size:15px;font-family:Arial;vertical-align:baseline;color:rgb(0,0,0)">RED HAT | DIFFERENT FOR THE SAKE OF BETTER TECHNOLOGY</span></p><p dir="ltr" style="margin:0px;padding:0px;border:0px;font-size:14px;font-family:"Helvetica Neue",Helvetica,Arial,"Lucida Grande",sans-serif;vertical-align:baseline;color:rgb(61,61,61);line-height:21px"><span style="margin:0px;padding:0px;border:0px;font-size:15px;font-family:Arial;vertical-align:baseline;color:rgb(0,0,0)">Find out why every airline, telecom, commercial bank, healthcare, and financial data services company in the Fortune 500 relies on Red Hat.</span></p><p dir="ltr" style="margin:0px;padding:0px;border:0px;font-size:14px;font-family:"Helvetica Neue",Helvetica,Arial,"Lucida Grande",sans-serif;vertical-align:baseline;color:rgb(61,61,61);line-height:21px"><span style="margin:0px;padding:0px;border:0px;font-size:15px;font-family:Arial;vertical-align:baseline;color:rgb(0,0,0)"><a href="https://www.redhat.com/en/about/trusted" rel="nofollow" style="margin:0px;padding:0px calc(12px + 0.35ex) 0px 0px;border:0px;font-weight:inherit;font-style:inherit;font-family:inherit;vertical-align:baseline;color:rgb(55,120,199);text-decoration:none" target="_blank">Trusted | Red Hat</a></span></p></div><div><br></div></div></div></div></div></div></div></div></div></div></div></div>
</div></div>