)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"dbbc9e84cfc093170e5e0ec656c8d3f58553c5d8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"8bc7aeff_225ece5f","updated":"2024-03-28 19:19:45.000000000","message":"I don\u0027t like this. We agreed in release team in the past that we keep the naming as it is, because our tools rely on the name and it might need a chain of refactorings if we replace this.\n\nEven if we want to move in this direction, this is not the right time to do it. Let\u0027s release 2024.1 Caracal first and then try the refactoring with proper testing all the tools we use during the process or outside of the process. The timing is not acceptable for this in my opinion.","commit_id":"f4a92598afa45ad72259fa99adcc0c3f9b51b3d8"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"2d6c644c6b928d2549c9e68acde2aa9808d8a399","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"cf6b1aff_5258a034","updated":"2024-04-05 07:28:27.000000000","message":"The release is now done, so the timing should be better?\n\nI don\u0027t agree to the assumption that the release team should stick do doing things differently than everyone else in the OpenStack world just because it happens to work. If there are issues with the switch, we should fix them instead, but currently I am not aware of any actual issues.","commit_id":"f4a92598afa45ad72259fa99adcc0c3f9b51b3d8"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"346d92f160f2d4b72c57855fedb7924383702781","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"18313097_84f8ca4f","updated":"2024-04-11 12:22:13.000000000","message":"This would break published links (for example, my recent communication to PTLs links to dalmatian/schedule.html), break tools and PROCESS.rst in several places (email templates for example), as well as prevent people from guessing the link by just substituting \"dalmatian\" for \"caracal\" in previously bookmarked links.\n\nIMHO this creates more confusion than it fixes, in addition to creating work for us to tie all the loose ends. It has taken us a year to close all the loose ends that moving from stable/antelope to stable/2023.1 has created (as predicted when the change was first proposed), I\u0027m not doing that again.","commit_id":"f4a92598afa45ad72259fa99adcc0c3f9b51b3d8"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"05c4673388d2f611c54e62df4c4535c5403caf84","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"082b160a_48a81afd","updated":"2024-03-28 16:23:46.000000000","message":"setting procedural ptl-approved flag for doc+data only change","commit_id":"f4a92598afa45ad72259fa99adcc0c3f9b51b3d8"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"0ab0bfe6d82f2579b4f619228220c5be0a257125","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"9b5a813c_811e77b1","in_reply_to":"8bc7aeff_225ece5f","updated":"2024-03-28 20:00:17.000000000","message":"I think way it will be easy as all other tooling are using numbers but I will leave it to release team.\n\nMy main/only concern is inconsistency is release notes page (main release notes page is with release name and project wise release notes pages are with release number)- https://etherpad.opendev.org/p/tc-2024.1-tracker#L56","commit_id":"f4a92598afa45ad72259fa99adcc0c3f9b51b3d8"}],"data/series_status.yaml":[{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"dbbc9e84cfc093170e5e0ec656c8d3f58553c5d8","unresolved":true,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"- name: \"2024.2\""},{"line_number":3,"context_line":"  release-id: 2024.2"},{"line_number":4,"context_line":"  status: future"},{"line_number":5,"context_line":"  initial-release: 2024-10-02"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"d60b65d6_b7894ac4","line":2,"updated":"2024-03-28 19:19:45.000000000","message":"iirc, this can be made to be resolved as string, like we did with the release id.","commit_id":"f4a92598afa45ad72259fa99adcc0c3f9b51b3d8"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"2e9f20eba9d47e3e36556213cf006849f8913050","unresolved":true,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"- name: \"2024.2\""},{"line_number":3,"context_line":"  release-id: 2024.2"},{"line_number":4,"context_line":"  status: future"},{"line_number":5,"context_line":"  initial-release: 2024-10-02"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"0daeea6c_61d76db4","line":2,"in_reply_to":"8b779911_851eaf54","updated":"2024-04-07 06:08:46.000000000","message":"I\u0027m very much in favor of also renaming the deliverables directory for consistency. My main concern however is to have the web site being present at https://releases.openstack.org/2024.2/index.html instead of https://releases.openstack.org/dalmatian/index.html, if you come up with some other solution that achieves that, I\u0027m fine to go with it.","commit_id":"f4a92598afa45ad72259fa99adcc0c3f9b51b3d8"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"1d6ba6de443c1600fc606874084f3991abdd1952","unresolved":true,"context_lines":[{"line_number":1,"context_line":"---"},{"line_number":2,"context_line":"- name: \"2024.2\""},{"line_number":3,"context_line":"  release-id: 2024.2"},{"line_number":4,"context_line":"  status: future"},{"line_number":5,"context_line":"  initial-release: 2024-10-02"}],"source_content_type":"text/x-yaml","patch_set":3,"id":"8b779911_851eaf54","line":2,"in_reply_to":"d60b65d6_b7894ac4","updated":"2024-04-05 14:52:27.000000000","message":"note, that replacing the \u0027name\u0027 with \u0027release-id\u0027 would need to change many(?) things. e.g. delvirables/dalmatian/ should be named deliverables/2024.2 instead, and then we should simply remove all the \u0027release-id\u0027 changes and refactor things to work with the new name. so one thing is this, another thing is what Thierry mentioned today on IRC (cycle name vs release name). also the release team agreed in the past that we keep the name as it was, and use the \u0027release-id\u0027 instead when we need the new numeric version format.\n\nrelease cores, please correct me, if i\u0027m wrong.","commit_id":"f4a92598afa45ad72259fa99adcc0c3f9b51b3d8"}]}