)]}'
{"zuul/layout.yaml":[{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"61b6fa356a4545909ed8ae8da610ed1b828b2716","unresolved":false,"context_lines":[{"line_number":2835,"context_line":"      - \u0027other-requirements.txt\u0027"},{"line_number":2836,"context_line":""},{"line_number":2837,"context_line":"  - name: ^gate-i18n-tox-doc-publish-docs.*$"},{"line_number":2838,"context_line":"    success-pattern: http://docs-draft.openstack.org/{build.parameters[LOG_PATH]}/publish-docs/developer/i18n"},{"line_number":2839,"context_line":""},{"line_number":2840,"context_line":"  - name: ^gate-.*-tox-doc-publish-checkbuild.*$"},{"line_number":2841,"context_line":"    success-pattern: http://docs-draft.openstack.org/{build.parameters[LOG_PATH]}/publish-docs/"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f1d235d_7b0e41e6","line":2838,"range":{"start_line":2838,"start_character":95,"end_line":2838,"end_character":109},"updated":"2017-06-29 16:58:00.000000000","message":"What I am not sure is how the ongoing doc migration affects the i18n guide path \"/developer/i18n\". Any advise would be appreciated.","commit_id":"852d7c500b7304fa4f73cd29831b66134fdb084b"},{"author":{"_account_id":14482,"name":"Ian Y. Choi","email":"ianyrchoi@gmail.com","username":"ianychoi"},"change_message_id":"5cba2e7ad8c9b920796ec5a0ed6c70baf691dcaf","unresolved":false,"context_lines":[{"line_number":2835,"context_line":"      - \u0027other-requirements.txt\u0027"},{"line_number":2836,"context_line":""},{"line_number":2837,"context_line":"  - name: ^gate-i18n-tox-doc-publish-docs.*$"},{"line_number":2838,"context_line":"    success-pattern: http://docs-draft.openstack.org/{build.parameters[LOG_PATH]}/publish-docs/developer/i18n"},{"line_number":2839,"context_line":""},{"line_number":2840,"context_line":"  - name: ^gate-.*-tox-doc-publish-checkbuild.*$"},{"line_number":2841,"context_line":"    success-pattern: http://docs-draft.openstack.org/{build.parameters[LOG_PATH]}/publish-docs/"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f1d235d_53e53e08","line":2838,"range":{"start_line":2838,"start_character":95,"end_line":2838,"end_character":109},"in_reply_to":"3f1d235d_1b9bc3c9","updated":"2017-07-04 12:32:39.000000000","message":"I have seen [1] and now I see that /i18n/latest/ should be right location. Since [2] has been merged, let\u0027s replace /developer/i18n with /i18n/latest .\n\n[1] http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/openstack-publish-jobs.yaml#n22\n[2] https://review.openstack.org/#/c/479473/","commit_id":"852d7c500b7304fa4f73cd29831b66134fdb084b"},{"author":{"_account_id":841,"name":"Akihiro Motoki","email":"amotoki@gmail.com","username":"amotoki"},"change_message_id":"efbb7a8eb60e1197970c7258526a79eb8771aa32","unresolved":false,"context_lines":[{"line_number":2835,"context_line":"      - \u0027other-requirements.txt\u0027"},{"line_number":2836,"context_line":""},{"line_number":2837,"context_line":"  - name: ^gate-i18n-tox-doc-publish-docs.*$"},{"line_number":2838,"context_line":"    success-pattern: http://docs-draft.openstack.org/{build.parameters[LOG_PATH]}/publish-docs/developer/i18n"},{"line_number":2839,"context_line":""},{"line_number":2840,"context_line":"  - name: ^gate-.*-tox-doc-publish-checkbuild.*$"},{"line_number":2841,"context_line":"    success-pattern: http://docs-draft.openstack.org/{build.parameters[LOG_PATH]}/publish-docs/"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f1d235d_1b9bc3c9","line":2838,"range":{"start_line":2838,"start_character":95,"end_line":2838,"end_character":109},"in_reply_to":"3f1d235d_264aed54","updated":"2017-06-29 22:45:37.000000000","message":"[memo for my memory]\n\n- the i18n doc job use upload-docs-draft macro [1] for check/gate job and \nupload-to-docs-site [2] as post job.\n- [2] assumes the build document is placed under publish-docs. If the expected path at docs.o.o is \u003cPATH\u003e, the build doc should be placed at publish-docs/\u003cPATH\u003e.\n- the i18n doc jobs always run \u0027docs\u0027 target in the i18n repo, so the build document patch needs to be same.\n- As a result, the build document in check/gate jobs would be publish-docs/\u003cPATH\u003e.\n\nSo, I think if we use /developer/i18n, publish-docs/developer/i18n is correct.\n\nIf we publish the i18n guide at /i18n/, the build document in check/gate jobs should be placed at publish-docs/i18n.\n\nWhat I need to clarify is the expected path in the new doc structure is /i18n/ or /i18n/latest/. The i18n repo is not expected to be branched, so I think either makes sense.\n\n[1] http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/macros.yaml#n1046\n[2] http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/jobs/macros.yaml#n1068","commit_id":"852d7c500b7304fa4f73cd29831b66134fdb084b"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"4c8b0d71c67619d02241599cfc8dc9ab570f93dd","unresolved":false,"context_lines":[{"line_number":2835,"context_line":"      - \u0027other-requirements.txt\u0027"},{"line_number":2836,"context_line":""},{"line_number":2837,"context_line":"  - name: ^gate-i18n-tox-doc-publish-docs.*$"},{"line_number":2838,"context_line":"    success-pattern: http://docs-draft.openstack.org/{build.parameters[LOG_PATH]}/publish-docs/developer/i18n"},{"line_number":2839,"context_line":""},{"line_number":2840,"context_line":"  - name: ^gate-.*-tox-doc-publish-checkbuild.*$"},{"line_number":2841,"context_line":"    success-pattern: http://docs-draft.openstack.org/{build.parameters[LOG_PATH]}/publish-docs/"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"3f1d235d_264aed54","line":2838,"range":{"start_line":2838,"start_character":95,"end_line":2838,"end_character":109},"in_reply_to":"3f1d235d_7b0e41e6","updated":"2017-06-29 18:58:33.000000000","message":"That path looks really wrong, see how the path looks in other cases.\n\nif you have /developer/i18n, it\u0027s wrong...\n\ndo you have a review for i18n up with this job?","commit_id":"852d7c500b7304fa4f73cd29831b66134fdb084b"}]}