)]}'
{"deliverables/wallaby/tripleo-validations.yaml":[{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"633bdf35eaa3c8c37d825f4f5a03e172a4c5c9c8","unresolved":true,"context_lines":[{"line_number":35,"context_line":"    projects:"},{"line_number":36,"context_line":"      - repo: openstack/tripleo-validations"},{"line_number":37,"context_line":"        hash: d74d3fc952aea6eda73192eb235217c3ba1052f3"},{"line_number":38,"context_line":"  - version: wallaby-em"},{"line_number":39,"context_line":"    projects:"},{"line_number":40,"context_line":"      - repo: openstack/tripleo-validations"},{"line_number":41,"context_line":"        hash: d74d3fc952aea6eda73192eb235217c3ba1052f3"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"31506e46_24237265","side":"PARENT","line":38,"range":{"start_line":38,"start_character":21,"end_line":38,"end_character":23},"updated":"2023-03-06 08:07:28.000000000","message":"have you discussed this with anyone on the release team i.e. is there some other context i\u0027m unaware of about a possible exception or workaround? Otherwise we can\u0027t make a new release upstream because the branch is tagged extended maintenance.","commit_id":"a3c26e656294fee0a19b5f3af0ad0542a74f9091"},{"author":{"_account_id":27427,"name":"David Peacock","email":"dpeacock@redhat.com","username":"davidjpeacock"},"change_message_id":"973d96a4918c4af6cd814850bece510ffeb7ceda","unresolved":true,"context_lines":[{"line_number":35,"context_line":"    projects:"},{"line_number":36,"context_line":"      - repo: openstack/tripleo-validations"},{"line_number":37,"context_line":"        hash: d74d3fc952aea6eda73192eb235217c3ba1052f3"},{"line_number":38,"context_line":"  - version: wallaby-em"},{"line_number":39,"context_line":"    projects:"},{"line_number":40,"context_line":"      - repo: openstack/tripleo-validations"},{"line_number":41,"context_line":"        hash: d74d3fc952aea6eda73192eb235217c3ba1052f3"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"6c8defe7_6617099a","side":"PARENT","line":38,"range":{"start_line":38,"start_character":21,"end_line":38,"end_character":23},"in_reply_to":"04533a21_d55777ef","updated":"2023-03-06 14:06:46.000000000","message":"Thanks Marios and Elod :-)\n\nPlease help me understand, is the problem that I clobbered -em or because I added version 14.3.2?\n\nIf it\u0027s possible, I can leave the -em in place and add 14.3.2 perhaps?","commit_id":"a3c26e656294fee0a19b5f3af0ad0542a74f9091"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"09a1497d4e88500a725d716a9b4288470853ec57","unresolved":true,"context_lines":[{"line_number":35,"context_line":"    projects:"},{"line_number":36,"context_line":"      - repo: openstack/tripleo-validations"},{"line_number":37,"context_line":"        hash: d74d3fc952aea6eda73192eb235217c3ba1052f3"},{"line_number":38,"context_line":"  - version: wallaby-em"},{"line_number":39,"context_line":"    projects:"},{"line_number":40,"context_line":"      - repo: openstack/tripleo-validations"},{"line_number":41,"context_line":"        hash: d74d3fc952aea6eda73192eb235217c3ba1052f3"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"04533a21_d55777ef","side":"PARENT","line":38,"range":{"start_line":38,"start_character":21,"end_line":38,"end_character":23},"in_reply_to":"31506e46_24237265","updated":"2023-03-06 12:34:26.000000000","message":"Thanks Marios. Yes as you say, this can\u0027t be released.","commit_id":"a3c26e656294fee0a19b5f3af0ad0542a74f9091"},{"author":{"_account_id":8449,"name":"Marios Andreou","email":"marios.andreou@gmail.com","username":"marios"},"change_message_id":"e2f66864390f8013dab9c0cb8ab6e87900daf7c4","unresolved":true,"context_lines":[{"line_number":35,"context_line":"    projects:"},{"line_number":36,"context_line":"      - repo: openstack/tripleo-validations"},{"line_number":37,"context_line":"        hash: d74d3fc952aea6eda73192eb235217c3ba1052f3"},{"line_number":38,"context_line":"  - version: wallaby-em"},{"line_number":39,"context_line":"    projects:"},{"line_number":40,"context_line":"      - repo: openstack/tripleo-validations"},{"line_number":41,"context_line":"        hash: d74d3fc952aea6eda73192eb235217c3ba1052f3"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"76411260_19aceaca","side":"PARENT","line":38,"range":{"start_line":38,"start_character":21,"end_line":38,"end_character":23},"in_reply_to":"6c8defe7_6617099a","updated":"2023-03-07 07:24:13.000000000","message":"My understanding is both, i.e. cannot tag 14.3.2 here and make an official release and we cannot clobber the -em.\n\nI am not sure however if we can do that *by ourselves* maybe the release folks Elod or anyone else can comment. i.e. can we push a 14.3.2 tag independently of this releases repo? In other words just git push a new 14.3.2 tag (probably via gerrit review on the tripleo-validations stable/wallaby branch? dont\u0027 think i\u0027ve ever done that before perhaps it is not possible).\n\nBut David perhaps we need to understand why we need the new tag here - i am assuming it is for some bug fix? \n\nDepending on whether we can push the tag ourselves, we can also consider trying to build the \u0027new\u0027 rdo tripleo-validations package from the commit hash directly (but i don\u0027t know what challenges this presents for rdo/packaging we would have to reach out to them about that).","commit_id":"a3c26e656294fee0a19b5f3af0ad0542a74f9091"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"dd17217f30881af11650a718dfbb7f7b60d8328e","unresolved":false,"context_lines":[{"line_number":35,"context_line":"    projects:"},{"line_number":36,"context_line":"      - repo: openstack/tripleo-validations"},{"line_number":37,"context_line":"        hash: d74d3fc952aea6eda73192eb235217c3ba1052f3"},{"line_number":38,"context_line":"  - version: wallaby-em"},{"line_number":39,"context_line":"    projects:"},{"line_number":40,"context_line":"      - repo: openstack/tripleo-validations"},{"line_number":41,"context_line":"        hash: d74d3fc952aea6eda73192eb235217c3ba1052f3"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"d50ba3b6_1be8acbb","side":"PARENT","line":38,"range":{"start_line":38,"start_character":21,"end_line":38,"end_character":23},"in_reply_to":"76411260_19aceaca","updated":"2023-03-07 10:45:40.000000000","message":"TL;DR: after a series transition to Extended Maintenance ($series-em), it won\u0027t accept upstream releases anymore.\n\nLong story: stable maintenance supported originally a series until ~1 year after its release. To make collaboration possible, Extended Maintenance process was introduced (and \u0027Maintained\u0027 phase increased to ~1.5 yrs). Extended Maintenance keeps the branches open for projects as long as they are maintained by the responsible project team. Extended Maintenance is somewhat different from a \u0027fully supported\u0027 maintained phase, for example there won\u0027t be official, coordinated upstream releases anymore for those branches, but vendors can consume merged patches and can do *downstream* releases out of the branches in extended maintenance.","commit_id":"a3c26e656294fee0a19b5f3af0ad0542a74f9091"}]}