)]}'
{"specs/xena/tripleo-independent-release.rst":[{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"6f914e7c00c434f092b092858d766a994b906392","unresolved":true,"context_lines":[{"line_number":39,"context_line":"party CI and the component and integration promotion pipelines [8]_, on an"},{"line_number":40,"context_line":"ongoing bases."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Finally, changes in the underlying OS between branches means that for some"},{"line_number":43,"context_line":"branches we maintain two \"types\" of CI job; for stable/train we have to support"},{"line_number":44,"context_line":"both Centos 7 and Centos 8. With the coming stable/xena, we would likely have"},{"line_number":45,"context_line":"to support Centos-Stream-8 as well as Centos-Stream-9 in the event that"},{"line_number":46,"context_line":"Stream-9 is not fully availably by the xena release."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"Proposed Change"},{"line_number":49,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"c61317e6_b95eea13","line":46,"range":{"start_line":42,"start_character":0,"end_line":46,"end_character":52},"updated":"2021-07-26 10:44:14.000000000","message":"It\u0027s not clear why this is a problem, nor is it clear why the change in release model solves the problem.","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"46f5066604eec50020a1c8f027d45e26e08af5d6","unresolved":true,"context_lines":[{"line_number":39,"context_line":"party CI and the component and integration promotion pipelines [8]_, on an"},{"line_number":40,"context_line":"ongoing bases."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"Finally, changes in the underlying OS between branches means that for some"},{"line_number":43,"context_line":"branches we maintain two \"types\" of CI job; for stable/train we have to support"},{"line_number":44,"context_line":"both Centos 7 and Centos 8. With the coming stable/xena, we would likely have"},{"line_number":45,"context_line":"to support Centos-Stream-8 as well as Centos-Stream-9 in the event that"},{"line_number":46,"context_line":"Stream-9 is not fully availably by the xena release."},{"line_number":47,"context_line":""},{"line_number":48,"context_line":"Proposed Change"},{"line_number":49,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"88f3752c_e535775f","line":46,"range":{"start_line":42,"start_character":0,"end_line":46,"end_character":52},"in_reply_to":"c61317e6_b95eea13","updated":"2021-07-28 16:37:31.000000000","message":"the previous paragraph lays that out no? \"This creates an ongoing maintenance and resource burden\". i will add some more words though see if you prefer the next version ;)","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"6f914e7c00c434f092b092858d766a994b906392","unresolved":true,"context_lines":[{"line_number":62,"context_line":"these are Train -\u003e Wallaby -\u003e Z?). For example it is highly likely that we"},{"line_number":63,"context_line":"would not create a Xena branch."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Developers will be freed from having to backport changes across stable/branches"},{"line_number":66,"context_line":"and this will have a dramatic effect on our upstream CI resource consumption"},{"line_number":67,"context_line":"and maintenance burden."},{"line_number":68,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"9d802db6_6eec3b73","line":65,"range":{"start_line":65,"start_character":0,"end_line":65,"end_character":10},"updated":"2021-07-26 10:44:14.000000000","message":"Developer of TripleO - this is distinct from the services that TripleO supports deploying.","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"46f5066604eec50020a1c8f027d45e26e08af5d6","unresolved":true,"context_lines":[{"line_number":62,"context_line":"these are Train -\u003e Wallaby -\u003e Z?). For example it is highly likely that we"},{"line_number":63,"context_line":"would not create a Xena branch."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Developers will be freed from having to backport changes across stable/branches"},{"line_number":66,"context_line":"and this will have a dramatic effect on our upstream CI resource consumption"},{"line_number":67,"context_line":"and maintenance burden."},{"line_number":68,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"49bf7a32_7e0ca06c","line":65,"range":{"start_line":65,"start_character":0,"end_line":65,"end_character":10},"in_reply_to":"817a8538_a367e1dd","updated":"2021-07-28 16:37:31.000000000","message":"@Jesse not following what the request is though you want me to elaborate on something here? \n\n@Bogdan how does it contradict. Developers won\u0027t have to cherrypick to branches that we choose not to create. We will continue to have cherrypicks and ci jobs and all that stuff for the branches we do create.","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":6926,"name":"Bogdan Dobrelya","email":"bdobreli@redhat.com","username":"bogdando"},"change_message_id":"cf6a9c1a538159e18e44c503a79f0fc892b342dc","unresolved":true,"context_lines":[{"line_number":62,"context_line":"these are Train -\u003e Wallaby -\u003e Z?). For example it is highly likely that we"},{"line_number":63,"context_line":"would not create a Xena branch."},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"Developers will be freed from having to backport changes across stable/branches"},{"line_number":66,"context_line":"and this will have a dramatic effect on our upstream CI resource consumption"},{"line_number":67,"context_line":"and maintenance burden."},{"line_number":68,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"817a8538_a367e1dd","line":65,"range":{"start_line":65,"start_character":0,"end_line":65,"end_character":10},"in_reply_to":"9d802db6_6eec3b73","updated":"2021-07-26 10:48:31.000000000","message":"be freed from backporting contradicts to the statement above \"focus our resources on those branches\nthat are most \u0027important\u0027 to us, namely the \u0027FFU branches\u0027.\"","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"6f914e7c00c434f092b092858d766a994b906392","unresolved":true,"context_lines":[{"line_number":65,"context_line":"Developers will be freed from having to backport changes across stable/branches"},{"line_number":66,"context_line":"and this will have a dramatic effect on our upstream CI resource consumption"},{"line_number":67,"context_line":"and maintenance burden."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Alternatives"},{"line_number":70,"context_line":"------------"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"477a0306_a4bffb5a","line":68,"updated":"2021-07-26 10:44:14.000000000","message":"TripleO does not just deploy OpenStack, but it also consumes OpenStack. How does this proposal affect the services/libraries it consumes?","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"46f5066604eec50020a1c8f027d45e26e08af5d6","unresolved":true,"context_lines":[{"line_number":65,"context_line":"Developers will be freed from having to backport changes across stable/branches"},{"line_number":66,"context_line":"and this will have a dramatic effect on our upstream CI resource consumption"},{"line_number":67,"context_line":"and maintenance burden."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Alternatives"},{"line_number":70,"context_line":"------------"},{"line_number":71,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"40d28a99_43ea4d25","line":68,"in_reply_to":"477a0306_a4bffb5a","updated":"2021-07-28 16:37:31.000000000","message":"right but say we decide not to create the X branch. Then we don\u0027t have any X ci jobs or periodic promotion jobs etc etc. SO we don\u0027t consume X from other repos/OpenStack services/libraries. ? In other words where will you consume those libraries we won\u0027t have any ci in place. \n\nWe will always be running those jobs (i.e. consuming ) for master branch, and any of the branches we choose to create. \n\nBasically we are saying that tripleo will no longer support all openstack releases.","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":6926,"name":"Bogdan Dobrelya","email":"bdobreli@redhat.com","username":"bogdando"},"change_message_id":"53a6a47678e50199c152d9371716924ed57e8811","unresolved":true,"context_lines":[{"line_number":70,"context_line":"------------"},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"We can continue to create all the stable/branches and use the same release"},{"line_number":73,"context_line":"model we currently have. This would mean we would continue to have an increased"},{"line_number":74,"context_line":"maintenance burden and would have to address that with increased resources."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Security Impact"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ccb73a57_c485e104","line":73,"updated":"2021-07-26 10:51:27.000000000","message":"please elaborate if there are more options for stable branches given that tripleo does not have to follow the stable branch policy, while staying in cycle-with-intermediary","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":6926,"name":"Bogdan Dobrelya","email":"bdobreli@redhat.com","username":"bogdando"},"change_message_id":"d328bb4d8ee34394b0a9c0df562bd4876d9ec103","unresolved":true,"context_lines":[{"line_number":70,"context_line":"------------"},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"We can continue to create all the stable/branches and use the same release"},{"line_number":73,"context_line":"model we currently have. This would mean we would continue to have an increased"},{"line_number":74,"context_line":"maintenance burden and would have to address that with increased resources."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Security Impact"}],"source_content_type":"text/x-rst","patch_set":2,"id":"d2747a38_ede89c20","line":73,"in_reply_to":"b0970226_2e921fd5","updated":"2021-07-29 11:08:24.000000000","message":"https://governance.openstack.org/tc/reference/tags/stable_follows-policy.html\nIF not following that policy, what options would remain for those who still prefers to stay in cycle-with-intermediary","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"46f5066604eec50020a1c8f027d45e26e08af5d6","unresolved":true,"context_lines":[{"line_number":70,"context_line":"------------"},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"We can continue to create all the stable/branches and use the same release"},{"line_number":73,"context_line":"model we currently have. This would mean we would continue to have an increased"},{"line_number":74,"context_line":"maintenance burden and would have to address that with increased resources."},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"Security Impact"}],"source_content_type":"text/x-rst","patch_set":2,"id":"b0970226_2e921fd5","line":73,"in_reply_to":"ccb73a57_c485e104","updated":"2021-07-28 16:37:31.000000000","message":"what do you have in mind Bogdan? \n\nI believe staying in cycle-with-intermediary means we are bound to create all the branches, up to 6 months delay from upstream is the limit i think.\n\nBUt that is the crucial difference that we are bound to create the branch and cannot decide not to. I have included this information on line 28 in the intro","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":14985,"name":"Alex Schultz","email":"aschultz@next-development.com","username":"mwhahaha"},"change_message_id":"bb85b92ff5ae20af0da742a689052447aee6d72c","unresolved":false,"context_lines":[{"line_number":131,"context_line":"Developer Impact"},{"line_number":132,"context_line":"----------------"},{"line_number":133,"context_line":""},{"line_number":134,"context_line":"Will have less stable/branches to backport fixes to."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Implementation"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3537ca40_cdeb0800","line":134,"updated":"2021-07-22 15:46:35.000000000","message":"I think there may also be an increased complexity when backporting as the changes may not exist in the previous FFU branch. We\u0027ve seen this when doing W-\u003eT backports where we renamed tripleo-ansible roles with _ instead of -. This will still be an issue and it\u0027s likely thatt he FFU backports will not be clean and require additional efforts to ensure they work corectly as we\u0027ll be having a about year an a half\u0027s worth of changes at the end of a FFU cycle from the previous one.  While there will be less backport patches, there will be an increased complexity for these patches.","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"c93bd1eecb54f832dff14775fc2414cdd9defe96","unresolved":false,"context_lines":[{"line_number":131,"context_line":"Developer Impact"},{"line_number":132,"context_line":"----------------"},{"line_number":133,"context_line":""},{"line_number":134,"context_line":"Will have less stable/branches to backport fixes to."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Implementation"}],"source_content_type":"text/x-rst","patch_set":2,"id":"9f940f29_dcd1889e","line":134,"in_reply_to":"242d8955_f7a7c71f","updated":"2021-07-23 14:22:17.000000000","message":"17:16 \u003c marios|ruck\u003e mwhahaha: k i can check again. i replied to your comment though I don\u0027t think it will be  *more* complex should be the same no? just skipping the in between bits. k thanks add  comments on the review and i will check and update next week\n17:16 \u003c mwhahaha\u003e it\u0027s more complex\n17:16 \u003c mwhahaha\u003e because the difference is much larger\n17:16 \u003c mwhahaha\u003e the drift exists between each single release today, but it\u0027s not as big as a 3 verrsion drift\n17:17 \u003c mwhahaha\u003e so it\u0027s less complex to resolve a single version backport than 3\n17:17 \u003c marios|ruck\u003e mwhahaha: the difference between U-T is larger than W-T but going W-T in both cases is the    same\n17:17 \u003c mwhahaha\u003e it\u0027s larger with more chance to screw up\n17:17 \u003c mwhahaha\u003e you get little validations each version W-\u003eV-\u003eU-\u003eT\n17:18 \u003c mwhahaha\u003e so the changes are 1) smaller and 2) validated at each phase\n17:18 \u003c marios|ruck\u003e mwhahaha: right that\u0027s what i mean about \"It might make it harder to follow the context   behind some of the larger diffs, without seeing the \u0027in between \u0027 bits but the diff should    be the same, i think?\"\n17:18 \u003c marios|ruck\u003e mwhahaha: k i can add some text aroudn that","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"46f5066604eec50020a1c8f027d45e26e08af5d6","unresolved":false,"context_lines":[{"line_number":131,"context_line":"Developer Impact"},{"line_number":132,"context_line":"----------------"},{"line_number":133,"context_line":""},{"line_number":134,"context_line":"Will have less stable/branches to backport fixes to."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Implementation"}],"source_content_type":"text/x-rst","patch_set":2,"id":"47c3b0e3_e63bbf95","line":134,"in_reply_to":"308f9f32_c8e91e42","updated":"2021-07-28 16:37:31.000000000","message":"yes you would skip the branches we choose not to create. not sure what your comment is about though are you agreeing? I will reword this a bit based on the conversation with alex earlier see if you like the next version.","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"2cb17dd14e53251ad0c60ecbb23f912e07e9d950","unresolved":false,"context_lines":[{"line_number":131,"context_line":"Developer Impact"},{"line_number":132,"context_line":"----------------"},{"line_number":133,"context_line":""},{"line_number":134,"context_line":"Will have less stable/branches to backport fixes to."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Implementation"}],"source_content_type":"text/x-rst","patch_set":2,"id":"242d8955_f7a7c71f","line":134,"in_reply_to":"3537ca40_cdeb0800","updated":"2021-07-23 14:14:20.000000000","message":"I agree about the possibility for bigger diff between 3 releases compared to 1 but I also think the situation will be no worse that it currently is and in fact a bit better.\n\nRight now we have to deal with those diffs e.g. w-\u003et *as well as* doing the backport in between. After this change we just skip the in between ones. The diff will have diverged the same after this change compared to without it youre just not doing victoria, and ussuri first before getting to train.\nIt might make it harder to follow the context behind some of the larger diffs, without seeing the \u0027in between \u0027 bits but the diff should be the same, i think?\n\nDo you think we need some text here about this?","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":14985,"name":"Alex Schultz","email":"aschultz@next-development.com","username":"mwhahaha"},"change_message_id":"23e9d8d55a08316e760e87310431e14f811308cf","unresolved":false,"context_lines":[{"line_number":131,"context_line":"Developer Impact"},{"line_number":132,"context_line":"----------------"},{"line_number":133,"context_line":""},{"line_number":134,"context_line":"Will have less stable/branches to backport fixes to."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Implementation"}],"source_content_type":"text/x-rst","patch_set":2,"id":"b8699321_0a29c1e1","line":134,"in_reply_to":"9f940f29_dcd1889e","updated":"2021-07-23 19:23:00.000000000","message":"Yea we just need to move some of the \u0027other end user impact\u0027 items here and explain that while we might have fewer cherry picks, we will end up with more complex conflict resolution.","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"},{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"6f914e7c00c434f092b092858d766a994b906392","unresolved":false,"context_lines":[{"line_number":131,"context_line":"Developer Impact"},{"line_number":132,"context_line":"----------------"},{"line_number":133,"context_line":""},{"line_number":134,"context_line":"Will have less stable/branches to backport fixes to."},{"line_number":135,"context_line":""},{"line_number":136,"context_line":""},{"line_number":137,"context_line":"Implementation"}],"source_content_type":"text/x-rst","patch_set":2,"id":"308f9f32_c8e91e42","line":134,"in_reply_to":"b8699321_0a29c1e1","updated":"2021-07-26 10:44:14.000000000","message":"Isn\u0027t tripleo-ansible part of TripleO, so the backport would still be a single branch - not stepping through multiple branches?","commit_id":"1baad2c142ca35403e6e4c844d26ba74c6d24e52"}]}