)]}'
{"doc/arch-design/storage_focus/section_tech_considerations_storage_focus.xml":[{"author":{"_account_id":7923,"name":"Gauvain Pocentek","email":"gauvainpocentek@gmail.com","username":"gpocentek"},"change_message_id":"1418881cc50225708060316f437f44c2459413f0","unresolved":false,"context_lines":[{"line_number":96,"context_line":"    \u003cpara\u003eWhen building a storage focused OpenStack architecture,"},{"line_number":97,"context_line":"        strive to build a flexible design that is based on an"},{"line_number":98,"context_line":"        industry standard core. One way of accomplishing this might be"},{"line_number":99,"context_line":"        through the use of different back-ends serving different use"},{"line_number":100,"context_line":"        cases.\u003c/para\u003e"},{"line_number":101,"context_line":"\u003c!--I feel like this last para just \u0027ends\u0027. Is there more information to be put here? A.S --\u003e"},{"line_number":102,"context_line":"\u003c/section\u003e"}],"source_content_type":"application/xml","patch_set":1,"id":"ba7be1f8_7e522768","line":99,"updated":"2015-03-03 06:23:34.000000000","message":"From our conventions this should be \"back end\" : https://wiki.openstack.org/wiki/Documentation/Conventions#backend.2C_back_end.2C_and_back-end","commit_id":"5933d1f730850b9848fb0b6ade5b10f16800c863"},{"author":{"_account_id":14947,"name":"Maria Zlatkova","email":"mzlatkova@mirantis.com","username":"mzlatkova"},"change_message_id":"d2d0a647aafe27209667ec47647ac08205868c2f","unresolved":false,"context_lines":[{"line_number":93,"context_line":"        \u003c/listitem\u003e"},{"line_number":94,"context_line":"      \u003c/varlistentry\u003e"},{"line_number":95,"context_line":"    \u003c/variablelist\u003e"},{"line_number":96,"context_line":"    \u003cpara\u003eWhen building a storage focused OpenStack architecture,"},{"line_number":97,"context_line":"        strive to build a flexible design that is based on an"},{"line_number":98,"context_line":"        industry standard core. One way of accomplishing this might be"},{"line_number":99,"context_line":"        through the use of different back ends serving different use"}],"source_content_type":"application/xml","patch_set":2,"id":"ba7be1f8_26388cd2","line":96,"updated":"2015-03-03 16:28:49.000000000","message":"I would change \"storage focused\" to \"storage-focused\"","commit_id":"1359639bc9c9a654b270c4e6fe660150143af710"},{"author":{"_account_id":7923,"name":"Gauvain Pocentek","email":"gauvainpocentek@gmail.com","username":"gpocentek"},"change_message_id":"087bdbe6ffd50ef747675d291f6da6ea947bf967","unresolved":false,"context_lines":[{"line_number":93,"context_line":"        \u003c/listitem\u003e"},{"line_number":94,"context_line":"      \u003c/varlistentry\u003e"},{"line_number":95,"context_line":"    \u003c/variablelist\u003e"},{"line_number":96,"context_line":"    \u003cpara\u003eWhen building a storage focused OpenStack architecture,"},{"line_number":97,"context_line":"        strive to build a flexible design that is based on an"},{"line_number":98,"context_line":"        industry standard core. One way of accomplishing this might be"},{"line_number":99,"context_line":"        through the use of different back ends serving different use"}],"source_content_type":"application/xml","patch_set":2,"id":"9a80dd14_67179252","line":96,"in_reply_to":"ba7be1f8_26388cd2","updated":"2015-03-04 05:36:50.000000000","message":"I agree with Maria\u0027s comment.\n\nDo you want to change this in this patch or another one?","commit_id":"1359639bc9c9a654b270c4e6fe660150143af710"}]}