<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Helvetica Neue";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1394504078;
mso-list-type:hybrid;
mso-list-template-ids:995385642 1572631088 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:%1-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Bruce, Release team;<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thank you for putting this in writing.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I have to admit I find the basic strategy statements confusing:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">1-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">We need to move away from time-based releases<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="color:#1F497D"><span style="mso-list:Ignore">2-<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">We need to do twice a year releases. This stmt, by definition, implies a time-gated release. Maybe it isn’t a specific date, but it is still time-gated.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">As a nascent project, I think we need to show gradual and consistent progress.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I did listen to much of the release team meeting today, and realize the trade-offs between big-rocks and timing are very difficult.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Given the difficult choice of functionality versus timing, I personally think we need to show progress in getting to Stein and a container based distribution as major milestones in 1H and perhaps defer the Distributed
Cloud capability to a 2H release. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I don’t see anything intrinsically wrong with moving a specific date out; it happens all the time. But I also think a release should have some gate; i.e. we don’t move out of 1H. And if some functionality isn’t
ready, then we move the functionality to another release in 2H.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Anyway, that would be my vote, if I have one.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Jones, Bruce E [mailto:bruce.e.jones@intel.com]
<br>
<b>Sent:</b> Thursday, March 28, 2019 12:49 PM<br>
<b>To:</b> starlingx-discuss<br>
<b>Subject:</b> [Starlingx-discuss] DRAFT release policy<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We’ve been working on a draft release policy in the Release team. Please review and share your comments, feedback or suggestions in the etherpad or on this thread.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The draft is located at <a href="https://etherpad.openstack.org/p/stx-release-policy-draft">
https://etherpad.openstack.org/p/stx-release-policy-draft</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The current text is below.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"> Brucej<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">Release Policy<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">===========<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">The StarlingX project determines release schedules based on when the release content is ready to be released. We should explicitly move away from the idea of time based
releases. We should continue our current twice per year release cycle<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.25in;text-indent:-.25in"><span style="font-size:10.0pt;font-family:Symbol;color:black">·</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:black">
</span><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">We should consider changing our release naming convention to something that doesn't include dates.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">The Release team, together with the Test team TLs/PLs, shall make a recommendation to the community and TSC that a release is ready to go. Upon TSC approval, the release
branches are tagged and the release documented.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">That recommendation should be based on:<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">1.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:black">
</span><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">Whether or not all anchor features in the release are complete, as per the input of the team(s) implementing the features and the results of Test team testing of the features<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.75in;text-indent:-.25in"><span style="font-size:10.0pt;font-family:Wingdings;color:black">§</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:black">
</span><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">Assumption: The TSC will create a list of approved features during the release planning process, and that some (or all) of these features will be identified by the TSC as "release
gating" or "anchor" features that would block a release if not complete.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.75in;text-indent:-.25in"><span style="font-size:10.0pt;font-family:Wingdings;color:black">§</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:black">
</span><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">Assumption: We are planning our releases at the PTG meetings every 6 months.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">2.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:black">
</span><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">The results of formal Testing performed by the Test team, measured by the percentage of planned tests attempted and the test pass rate<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.75in;text-indent:-.25in"><span style="font-size:10.0pt;font-family:Wingdings;color:black">§</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:black">
</span><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">Proposal: 100% test cases attemped and 95% test cases passing in all configurations<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:-.25in"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">3.</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:black">
</span><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">The severity and number of bugs open against the release<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.75in;text-indent:-.25in"><span style="font-size:10.0pt;font-family:Wingdings;color:black">§</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:black">
</span><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">Proposal: No open Critical or High severity bugs against the release candidate. Or maybe 1-3 Highs if we have a clear resolution plan (and a plan to release a patch against the release?)<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.75in;text-indent:-.25in"><span style="font-size:10.0pt;font-family:Wingdings;color:black">§</span><span style="font-size:7.0pt;font-family:"Times New Roman","serif";color:black">
</span><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">See Bug Severity definitions below.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">We should discuss the option of doing a mid-cycle “bug fix” release against the latest release – allowing key defects to get fixed more rapidly. In such a case, the
release team would make a recommendation to the TSC to approve the release plan and content. If approved by the TSC, the fixes shall be cherry-picked or merged into the release branch and a new build tested (and managed as per this policy).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">Bug Severity<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">==========<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">Critical</span></b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">: The software does not operate as intended (e.g. the software fails to
install, does not run, crashes, etc...). Or the issue is a Securty/CVE issue with a rating of Critical or High. In Launchpad this is "Fix as soon as possible"<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">High</span></b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">: An important feature of the software does not operate as intended (e.g. live
migration, fault reporting, etc...). Or the issue is a Security/CVE issue with a rating of Medium or lower. In Launchpad this is "Fix soon".<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">Medium</span></b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">: A minor feature of the software does not operate as intended or there is
an intermitant failure. In Launchpad this is "Fix when convienent or schedule to fix later".<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">Low</span></b><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black">: A bug that does not impact normal operation of the software. In Launchpad
this is "Fix when convienent".<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Helvetica Neue";color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>