<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hello Helen,<br>
<br>
Thanks a lot for sharing a string freeze exception request to
openstack-dev mailing list.<br>
<br>
With @amotoki's comment [1] and the discussion on the last IRC
meeting yesterday [2],<br>
I18n team is fine and there will be no problem to accept the
requests from I18n team's perspective.<br>
<br>
Note that String Freeze has been important for Docs & I18n
team to acknowledge string freeze<br>
status and take appropriate actions of what needs to be changed to
documentation and translation activities if needed.<br>
Since I18n team now more focuses on dashboard translations [1] and
documents are being migrated [3],<br>
I think the importance of string freeze for server projects (e.g.,
cinder, nova, keystone, neutron) might<br>
be less important than previous cycle(s), but sharing the status
to all the teams including release management team<br>
is a good idea to stay on the same page as much as possible :)<br>
<br>
<br>
With many thanks,<br>
<br>
/Ian, I18n team Ocata PTL.<br>
<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-i18n/2017-August/002999.html">http://lists.openstack.org/pipermail/openstack-i18n/2017-August/002999.html</a><br>
[2]
<a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/openstack_i18n_meeting.2017-08-03-13.02.html">http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/openstack_i18n_meeting.2017-08-03-13.02.html</a><br>
[3]
<a class="moz-txt-link-freetext" href="http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html">http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html</a><br>
<br>
Walsh, Helen wrote on 8/3/2017 5:21 PM:<br>
</div>
<blockquote type="cite"
cite="mid:6031C821D2144A4CB722005A21B34BD53AB13988@MX202CL02.corp.emc.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
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:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle22
{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:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>To whom it may concern,<o:p></o:p></b></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">I
would like to request a string freeze exception for 2
patches that are on the merge queue for Pike.<o:p></o:p></span></p>
<p class="MsoListParagraph"><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt"><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">1.</span><span
style="font-size:7.0pt;font-family:"Times New
Roman",serif;color:black">
</span><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">VMAX
driver - align VMAX QOS settings with front end (CI Passed)<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:18.0pt"><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><a
href="https://review.openstack.org/#/c/484885/7/cinder/volume/drivers/dell_emc/vmax/rest.py"
target="_blank" moz-do-not-send="true">https://review.openstack.org/#/c/484885/7/cinder/volume/drivers/dell_emc/vmax/rest.py</a>
line 800 (removal of exception message)<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-indent:18.0pt"><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">Although
it’s primary aim is to align QoS with front end setting it
indirectly fixes a lazy loading error we were seeing around
QoS which occasionally<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:18.0pt"><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif;color:black">Broke
CI on previous patches.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoListParagraph" style="text-indent:-18.0pt">2.<span
style="font-size:7.0pt;font-family:"Times New
Roman",serif">
</span>VMAX driver - seamless upgrade from SMI-S to REST (CI
Pending)<o:p></o:p></p>
<p class="MsoNormal" style="text-indent:18.0pt"><a
href="https://review.openstack.org/#/c/482138/19/cinder/volume/drivers/dell_emc/vmax/common.py"
moz-do-not-send="true">https://review.openstack.org/#/c/482138/19/cinder/volume/drivers/dell_emc/vmax/common.py</a>
line 1400 ,1455 (message changes)<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:18.0pt">This is vital
for as reuse of volumes from Ocata to Pike. In Ocata we used
SMIS to interface with the VMAX, in Pike we are using REST. A
few changes needed to be made to make this transition as
seamless as possible.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you,<o:p></o:p></p>
<p class="MsoNormal">Helen<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>