)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"60d763630946eb844eabfc53a8394df4b7933232","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f7a5e5b2_adef7402","updated":"2025-06-27 16:35:37.000000000","message":"I agree that we do not need to maintain these deliverables and we already have warning about sdk sa replacement in their README.\n\nAs they are master only branches (no stable branch/release), deprecation and retirement is same.\n\nThe main difference between Deprecation and Retirement is only if deliverables have and want to maintain stable branches. From master branch, there is no difference as in both case you need to remove the master content.\n \n- https://docs.openstack.org/project-team-guide/repository.html#deprecating-a-repository\n- https://docs.openstack.org/project-team-guide/repository.html#retiring-a-repository\n\nIf you think README warnings were not official deprecation warning and we need to have a official deprecation flag in governance then I am ok to have deprecation flag in this cycle and in future cycle we can retire it. I think this can be applicable for many other master-only deliverbales and its good opportunity to improve deprecation guide/process also on same line. Do let me know how you would like to proceed and I can chnage my vote.","commit_id":"92c567ccdd07fe9675826f65d168a5e6b9e4ac32"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"7fa722bd73cb6b320dca4356fd39c9534d13d89c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"49529242_6d5b9ce6","updated":"2025-06-27 10:46:53.000000000","message":"just a note that opendev is still actively using glean for the images running in the CI, but IMO this should not block the deprecation in the openstack context. I assume the opendev team could adopt the repo under a different umbrella if needed","commit_id":"92c567ccdd07fe9675826f65d168a5e6b9e4ac32"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b9ec5f9a1d6848ba3a859c1e68ac2513e3dd5a6f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"bbe46c36_e8dc182b","in_reply_to":"c2a28f3f_6447b59c","updated":"2025-07-09 17:26:12.000000000","message":"yeah, for retirement content of master needs to be deleted. I am ok with your plan, I think that is fine to keep them deprecated for the purpose you described.","commit_id":"92c567ccdd07fe9675826f65d168a5e6b9e4ac32"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"ddc2ce8725fb1babc04b32e2fa69e3571bda98f7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c2a28f3f_6447b59c","in_reply_to":"f7a5e5b2_adef7402","updated":"2025-06-30 15:22:20.000000000","message":"I\u0027m happy to do either. Personally, keeping the branches around means we can address easy issues if absolutely necessary, but I want to signal that we won\u0027t do anything more than that. I assume if we retire it, the contents of the `master` branch is deleted so we can\u0027t do that?","commit_id":"92c567ccdd07fe9675826f65d168a5e6b9e4ac32"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b9ec5f9a1d6848ba3a859c1e68ac2513e3dd5a6f","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"c19e3aff_593abf47","updated":"2025-07-09 17:26:12.000000000","message":"lgtm","commit_id":"8ae1e276cea2e54342fba035a28c94b083aa1e2d"}]}