)]}'
{"deliverables/victoria/os-refresh-config.yaml":[{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"eb4d78272345cf1a1cd0fad282d8c81278910ac7","unresolved":true,"context_lines":[{"line_number":7,"context_line":"repository-settings:"},{"line_number":8,"context_line":"  openstack/os-refresh-config: {}"},{"line_number":9,"context_line":"releases:"},{"line_number":10,"context_line":"  - version: 12.0.0"},{"line_number":11,"context_line":"    projects:"},{"line_number":12,"context_line":"      - repo: openstack/os-refresh-config"},{"line_number":13,"context_line":"        hash: 754bb751e6728aafa680111a6fab3013609654cc"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"a72c5b49_b6615f50","line":10,"range":{"start_line":10,"start_character":13,"end_line":10,"end_character":15},"updated":"2021-01-08 12:43:17.000000000","message":"not sure about that one @Herve. The last tag there is Train on 10.4.0 https://github.com/openstack/os-refresh-config/tags \nlooks like there was no ussuri release. that would have been 11. so that is why i chose to call victoria \u002712\u0027. is that legal? ;) wdyt?\n\nreally the problem is that we aren\u0027t even using these any longer, with the exception of tripleo-ipsec i believe. for the os-refresh-config and os-colllect-config i think we should really retire them/ move those repos to EOL so we don\u0027t have to release them. Unless someone else is using of course but I don\u0027t think that is the case. At least no one is complaining about the lack of branches eg. no ussuri @ https://github.com/openstack/os-refresh-config/branches","commit_id":"4df318808c7591be3346a96c87fe4b0c0c1e3508"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"5a18ea43d6bff805ba5a44ff5dbcdba6ba854da5","unresolved":true,"context_lines":[{"line_number":7,"context_line":"repository-settings:"},{"line_number":8,"context_line":"  openstack/os-refresh-config: {}"},{"line_number":9,"context_line":"releases:"},{"line_number":10,"context_line":"  - version: 12.0.0"},{"line_number":11,"context_line":"    projects:"},{"line_number":12,"context_line":"      - repo: openstack/os-refresh-config"},{"line_number":13,"context_line":"        hash: 754bb751e6728aafa680111a6fab3013609654cc"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"d02fb308_a0433ee1","line":10,"range":{"start_line":10,"start_character":13,"end_line":10,"end_character":15},"in_reply_to":"a72c5b49_b6615f50","updated":"2021-01-08 13:08:37.000000000","message":"I think we could proceed as it was already did with some of your repos during train:\n\nhttps://review.opendev.org/c/openstack/releases/+/697542/\n\nHowever I think we need further changes as alredy did recently moltiron [1][2].\n\nTo do that you simply need to add the following line just before the `repos` key [3] (c.f a real example [1]):\n\n```\nrelease-management: none\n```\n\nAnd then we will be able to remove this file.\n\nI think it could be done on a separated patch that this one, to avoid to mix topics.\nAlso don\u0027t forget to add a `depends-on` that point on the governance patch to allow us merge them accordingly.\nHowever all the abandons could be done into a single one patch.\n\nThanks.\n\nHopefully I answering your questions.\n\n[1] https://review.opendev.org/c/openstack/governance/+/769805\n[2] https://review.opendev.org/c/openstack/releases/+/769597\n[3] https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml#L3080-L3082","commit_id":"4df318808c7591be3346a96c87fe4b0c0c1e3508"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"24690c76b3ec4da50a434d45e5c75867747b2bc9","unresolved":true,"context_lines":[{"line_number":7,"context_line":"repository-settings:"},{"line_number":8,"context_line":"  openstack/os-refresh-config: {}"},{"line_number":9,"context_line":"releases:"},{"line_number":10,"context_line":"  - version: 12.0.0"},{"line_number":11,"context_line":"    projects:"},{"line_number":12,"context_line":"      - repo: openstack/os-refresh-config"},{"line_number":13,"context_line":"        hash: 754bb751e6728aafa680111a6fab3013609654cc"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"ebdda2a3_72f46fb0","line":10,"range":{"start_line":10,"start_character":13,"end_line":10,"end_character":15},"in_reply_to":"d02fb308_a0433ee1","updated":"2021-01-08 14:00:46.000000000","message":"\u003cSNIP\u003e\n\n\u003e And then we will be able to remove this file.\n\u003e \n\u003e I think it could be done on a separated patch that this one, to avoid to mix topics.\n\u003e Also don\u0027t forget to add a `depends-on` that point on the governance patch to allow us merge them accordingly.\n\u003e However all the abandons could be done into a single one patch.\n\n\nso to be clear, do you suggest we go ahead with this and release stable/victoria since we have the deadline next week, and currently these projects are listed in governance.\n\nThen next week for example I can follow up with the governance change to make so we can remove the release file ?\n\nThat makes sense to me.\n\nOr, we don\u0027t make the release at all, and just go ahead with the changes required to remove.\n\n\n\n\n\n\u003e \n\u003e Thanks.\n\u003e \n\u003e Hopefully I answering your questions.\n\u003e \n\u003e [1] https://review.opendev.org/c/openstack/governance/+/769805\n\u003e [2] https://review.opendev.org/c/openstack/releases/+/769597\n\u003e [3] https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml#L3080-L3082","commit_id":"4df318808c7591be3346a96c87fe4b0c0c1e3508"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"27a0134338f6b23e2d76145765c90614e468323d","unresolved":true,"context_lines":[{"line_number":7,"context_line":"repository-settings:"},{"line_number":8,"context_line":"  openstack/os-refresh-config: {}"},{"line_number":9,"context_line":"releases:"},{"line_number":10,"context_line":"  - version: 12.0.0"},{"line_number":11,"context_line":"    projects:"},{"line_number":12,"context_line":"      - repo: openstack/os-refresh-config"},{"line_number":13,"context_line":"        hash: 754bb751e6728aafa680111a6fab3013609654cc"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"dba56303_1e450672","line":10,"range":{"start_line":10,"start_character":13,"end_line":10,"end_character":15},"in_reply_to":"d295a4d3_8d0eb7ae","updated":"2021-01-11 12:01:03.000000000","message":"o/ Herve I\u0027ve been thinking about what the right thing to do here is. In all 3 cases the changes since the last release are around testing. [1]\n\nFor os-refresh-config and os-collect-config I am certain we aren\u0027t using these any more in the \u0027normal\u0027 tripleo deployment case. Though we\u0027ve said it before, we haven\u0027t actually started a conversation with the community to see if anyone minds that we stop releasing these altogether. I think we need to have that conversation first before posting the change to governance and making these repos as \"release-management: none\".\n\nIn my opinion it is \u0027safer\u0027 to create the victoria branch and make this stable/victoria release now since we are on a deadline of this week to do so. At the same time I can start the conversation via mailing list and our next tripleo irc meeting (next Tuesday 19th) to see if there is any objection to making the governance changes. I just sent [2] to the list about this issue,\n\n[1] https://pastebin.com/raw/KJ0JxKPx \n[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019751.html","commit_id":"4df318808c7591be3346a96c87fe4b0c0c1e3508"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"51880e9b21f26efb43e22d75d1b8214d60caca58","unresolved":true,"context_lines":[{"line_number":7,"context_line":"repository-settings:"},{"line_number":8,"context_line":"  openstack/os-refresh-config: {}"},{"line_number":9,"context_line":"releases:"},{"line_number":10,"context_line":"  - version: 12.0.0"},{"line_number":11,"context_line":"    projects:"},{"line_number":12,"context_line":"      - repo: openstack/os-refresh-config"},{"line_number":13,"context_line":"        hash: 754bb751e6728aafa680111a6fab3013609654cc"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"21af90e2_89a4fc53","line":10,"range":{"start_line":10,"start_character":13,"end_line":10,"end_character":15},"in_reply_to":"dba56303_1e450672","updated":"2021-01-11 12:55:15.000000000","message":"Ack no problem, you are right it could be less intrusive to create the victoria branch for them, it could be a smoother step toward the abandon, but no rush, first we can wait a bit for feedbacks on http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019751.html . The deadline is January 14.","commit_id":"4df318808c7591be3346a96c87fe4b0c0c1e3508"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"8882b66d885b12ee2133682ef41ef9624be68abf","unresolved":true,"context_lines":[{"line_number":7,"context_line":"repository-settings:"},{"line_number":8,"context_line":"  openstack/os-refresh-config: {}"},{"line_number":9,"context_line":"releases:"},{"line_number":10,"context_line":"  - version: 12.0.0"},{"line_number":11,"context_line":"    projects:"},{"line_number":12,"context_line":"      - repo: openstack/os-refresh-config"},{"line_number":13,"context_line":"        hash: 754bb751e6728aafa680111a6fab3013609654cc"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"d295a4d3_8d0eb7ae","line":10,"range":{"start_line":10,"start_character":13,"end_line":10,"end_character":15},"in_reply_to":"ebdda2a3_72f46fb0","updated":"2021-01-08 14:30:42.000000000","message":"\u003e \u003cSNIP\u003e\n\u003e \n\u003e \u003e And then we will be able to remove this file.\n\u003e \u003e \n\u003e \u003e I think it could be done on a separated patch that this one, to avoid to mix topics.\n\u003e \u003e Also don\u0027t forget to add a `depends-on` that point on the governance patch to allow us merge them accordingly.\n\u003e \u003e However all the abandons could be done into a single one patch.\n\u003e \n\u003e \n\u003e so to be clear, do you suggest we go ahead with this and release stable/victoria since we have the deadline next week, and currently these projects are listed in governance.\n\u003e \n\u003e Then next week for example I can follow up with the governance change to make so we can remove the release file ?\n\u003e \n\u003e That makes sense to me.\n\u003e \n\u003e Or, we don\u0027t make the release at all, and just go ahead with the changes required to remove.\n\u003e \n\nHere is the list of changes that will be landed if we decide to continue:\n\n* 754bb75 Replace deprecated UPPER_CONSTRAINTS_FILE variable\n* 8a74797 Bump pyflakes\n* 2d6a974 Cleanup py27 support\n* b324bce Use unittest.mock instead of third party mock\n* cc543ed Stop testing python2.7\n* 84d8464 Switch to Ussuri jobs\n\nIf no significant changes have been merged since the latest release of them, then yes I think we can just go ahead with the changes required to remove.\n\nAnd since these projects haven\u0027t been branched for ussuri and since changes not yet released are just updates around testing and repo setup and related things I think we can ignore them. In other words I didn\u0027t see new features or fixes not yet released.\n\nI\u0027m not fan to release just to release... and even more a major version here...\n\nSo yes I think we can leave them, if we have nothing to release then I would suggest to ignore them for victoria and simply remove them now. \n\nThanks for the given details.\n\n\u003e \n\u003e \n\u003e \n\u003e \n\u003e \u003e \n\u003e \u003e Thanks.\n\u003e \u003e \n\u003e \u003e Hopefully I answering your questions.\n\u003e \u003e \n\u003e \u003e [1] https://review.opendev.org/c/openstack/governance/+/769805\n\u003e \u003e [2] https://review.opendev.org/c/openstack/releases/+/769597\n\u003e \u003e [3] https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml#L3080-L3082","commit_id":"4df318808c7591be3346a96c87fe4b0c0c1e3508"}]}