<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style>
<!--
@font-face
        {font-family:"Cambria Math"}
@font-face
        {font-family:Calibri}
@font-face
        {font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Calibri",sans-serif}
a:link, span.MsoHyperlink
        {color:#0563C1;
        text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
        {color:#954F72;
        text-decoration:underline}
p
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif}
p.msochpdefault, li.msochpdefault, div.msochpdefault
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri",sans-serif}
span.emailstyle17
        {font-family:"Calibri",sans-serif;
        color:windowtext}
span.msoins
        {color:teal;
        text-decoration:underline}
span.EmailStyle21
        {font-family:"Calibri",sans-serif;
        color:windowtext}
span.msoIns
        {text-decoration:underline;
        color:teal}
.MsoChpDefault
        {font-size:10.0pt}
@page WordSection1
        {margin:1.0in 1.0in 1.0in 1.0in}
-->
</style><style type="text/css" id="owaParaStyle">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body fpstyle="1" ocsi="0" vlink="#954F72" link="#0563C1" lang="EN-US" bgcolor="white">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">
<div>Yes, IIRC we agreed (during Arch Committee meeting) about releasing as much 1.1.X releases as we want since they will only include bug fixes.</div>
<div><br>
</div>
<div>Now, on a side note, we'll hit the topic of creating a new branch when we'll have a change breaking the compatibility, but that we'll want to still get the bug fixes into new releases. That's where the complexity starts and where we need to decide about
 a backporting plan.</div>
<div><br>
</div>
<div>Thanks,<br>
</div>
<div>Sebastien<br>
</div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF583262" style="direction: ltr;"><font size="2" face="Tahoma" color="#000000"><b>From:</b> Ernst, Eric [eric.ernst@intel.com]<br>
<b>Sent:</b> Wednesday, July 18, 2018 11:10 AM<br>
<b>To:</b> Fox, Kevin M; Venegas Munoz, Jose Carlos; akapoor87@gmail.com; rajudev<br>
<b>Cc:</b> kata-dev@lists.katacontainers.io<br>
<b>Subject:</b> Re: [kata-dev] [kata-release] release cadence, process<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Assuming that the release isn’t changing any APIs, etc.  If its just a bug fix, it would allow this. 
</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">If any incompat is introduced it’d be a 0.x.0 update.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">--Eric</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span></p>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-left:.5in"><b><span style="color:black">From: </span>
</b><span style="color:black">"Fox, Kevin M" <Kevin.Fox@pnnl.gov><br>
<b>Date: </b>Wednesday, July 18, 2018 at 11:09 AM<br>
<b>To: </b>Eric Ernst <eric.ernst@intel.com>, "Venegas Munoz, Jose Carlos" <jose.carlos.venegas.munoz@intel.com>, "akapoor87@gmail.com" <akapoor87@gmail.com>, rajudev <rajudev@disroot.org><br>
<b>Cc: </b>"kata-dev@lists.katacontainers.io" <kata-dev@lists.katacontainers.io><br>
<b>Subject: </b>RE: [kata-release] release cadence, process</span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt"> </span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:10.0pt; font-family:"Tahoma",sans-serif; color:black">Based on your 0.0.x comment, I think I know, but am verifying...<br>
<br>
This would still allow upgrading some components while running older components on the same host?<br>
<br>
Thanks,<br>
Kevin</span></p>
<div>
<div class="MsoNormal" style="margin-left:.5in; text-align:center" align="center">
<span style="font-family:"Times New Roman",serif; color:black">
<hr width="100%" size="2" align="center">
</span></div>
<div id="divRpF168137">
<p class="MsoNormal" style="margin-right:0in; margin-bottom:12.0pt; margin-left:.5in">
<b><span style="font-size:10.0pt; font-family:"Tahoma",sans-serif; color:black">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma",sans-serif; color:black"> Ernst, Eric [eric.ernst@intel.com]<br>
<b>Sent:</b> Wednesday, July 18, 2018 10:59 AM<br>
<b>To:</b> Venegas Munoz, Jose Carlos; akapoor87@gmail.com; rajudev<br>
<b>Cc:</b> kata-dev@lists.katacontainers.io<br>
<b>Subject:</b> [kata-dev] [kata-release] release cadence, process</span><span style="font-family:"Times New Roman",serif; color:black"></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt; color:black">Carlos et al,</span><span style="color:black"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt; color:black"> </span><span style="color:black"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt; color:black">I am proposing that we continue to roll releases; we are having a good amount of fixes merge and I think it warrants having a regular weekly cadence (likely a 0.0.x update). 
 I believe we discussed this before – let’s start driving it.</span><span style="color:black"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt; color:black"> </span><span style="color:black"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt; color:black">Carlos, Raju, Akshay – from prior emails/request for volunteers, you were all listed for folks to help with packaging and release.  Carlos, is the process defined enough
 that you think we can start rotating the release duties among more stakeholders?</span><span style="color:black"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt; color:black"> </span><span style="color:black"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt; color:black">WDYT?</span><span style="color:black"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt; color:black"> </span><span style="color:black"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt; color:black">Thx,</span><span style="color:black"></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt; color:black">Eric</span><span style="color:black"></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>