Open Stack

Hello Helen,

Thanks a lot for sharing a string freeze exception request to 
openstack-dev mailing list.

With @amotoki's comment [1] and the discussion on the last IRC meeting 
yesterday [2],
I18n team is fine and there will be no problem to accept the requests 
from I18n team's perspective.

Note that String Freeze has been important for Docs & I18n team to 
acknowledge string freeze
status and take appropriate actions of what needs to be changed to 
documentation and translation activities if needed.
Since I18n team now more focuses on dashboard translations [1] and 
documents are being migrated [3],
I think the importance of string freeze for server projects (e.g., 
cinder, nova, keystone, neutron) might
be less important than previous cycle(s), but sharing the status to all 
the teams including release management team
is a good idea to stay on the same page as much as possible :)


With many thanks,

/Ian, I18n team Ocata PTL.


[1] 
http://lists.openstack.org/pipermail/openstack-i18n/2017-August/002999.html
[2] 
http://eavesdrop.openstack.org/meetings/openstack_i18n_meeting/2017/openstack_i18n_meeting.2017-08-03-13.02.html
[3] 
http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html

Walsh, Helen wrote on 8/3/2017 5:21 PM:
>
> *To whom it may concern,*
>
> I would like to request a string freeze exception for 2 patches that 
> are on the merge queue for Pike.
>
> 1.VMAX driver - align VMAX QOS settings with front end  (CI Passed)
>
> https://review.openstack.org/#/c/484885/7/cinder/volume/drivers/dell_emc/vmax/rest.py 
> line 800 (removal of exception message)
>
> 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
>
> Broke CI on previous patches.
>
> 2.VMAX driver - seamless upgrade from SMI-S to REST (CI Pending)
>
> https://review.openstack.org/#/c/482138/19/cinder/volume/drivers/dell_emc/vmax/common.py 
> line 1400 ,1455 (message changes)
>
> 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.
>
> Thank you,
>
> Helen
>
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170805/27ad9a66/attachment.html>