I am not sure who is responsible to respond to string freeze exception, but I will comment it as my hat of the i18n team.
Looking at "cinder" translation status , the best progress is ~73% and 718 of 2932 message are remaining. In other languages the progress is lower. Adding two new messages does not matter. Removing messages has no problem. I see no blocking issue in this request. In addition, I think the i18n team focuses on dashboard translations and server projects are less focused for translations. IIRC the I18n team discussed an idea to announce the i18n team focus on translation to let server projects be free from string freeze around the beginning of the Pike cycle but I am not sure it is announced or not. Thanks, Akihiro  https://translate.openstack.org/iteration/view/cinder/master/documents?docId=cinder%2Flocale%2Fcinder&dswid=5769 2017-08-03 3:14 GMT+09:00 Walsh, Helen <helen.wa...@dell.com>: > > > > > 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-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev