)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"5da260f7afa2d9b7f0e998d5cabd59d03d01cc68","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"9242e6aa_a28f0360","updated":"2023-04-11 04:24:16.000000000","message":"Again I do not intend to block this work, but just trying to clarify the policy documented. If the project team agrees with this backport then feel free to merge it.","commit_id":"bffc0ef7a2edd496c2779dcb944f05488820b5e1"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"924a67f170e35c8ed4cc4d40017af1756b18f6f1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"34bd7b83_9e2f48fa","updated":"2023-03-17 07:27:30.000000000","message":"I\u0027m not a telemetry core so I won\u0027t block this backport but basically we should not backport a new feature to stable branches. Interestingly Telemetry does not follow stable policy it seems but my personal expectation is that it should do to be aligned with the other core projects.\n\nhttps://docs.openstack.org/project-team-guide/stable-branches.html","commit_id":"bffc0ef7a2edd496c2779dcb944f05488820b5e1"},{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"b8024bf8a2bdc56fdfcc7d1a476a4a5d0aeb4621","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"256bf202_7a2eec15","updated":"2023-04-13 07:30:16.000000000","message":"In my view, even backporting features is okay, as long as you won\u0027t break existing users, and that\u0027s the case here.","commit_id":"bffc0ef7a2edd496c2779dcb944f05488820b5e1"},{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"eb385ac837cd674150f8ff1b43271e497a98799b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"238b979c_f5a03f85","updated":"2023-03-17 07:55:21.000000000","message":"Telemetry not following stable policy is a good find; however I considered us following stable policy.\n\nFor this patch: the additional data is disabled by default; it doesn\u0027t change anything for existing deployments.","commit_id":"bffc0ef7a2edd496c2779dcb944f05488820b5e1"},{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"0e272641e2c0de4913166ac4d4a5a12dfc11660d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"75c4a8d4_4c4de1c4","updated":"2023-04-13 13:41:24.000000000","message":"recheck","commit_id":"bffc0ef7a2edd496c2779dcb944f05488820b5e1"},{"author":{"_account_id":32240,"name":"Yadnesh Kulkarni","email":"yadnesh_kulkarni@proton.me","username":"ykulkarn"},"change_message_id":"c27700620dda1f59574ded35dc846847ef9c180b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"84dc5555_4b991d5c","updated":"2023-04-17 05:10:05.000000000","message":"recheck","commit_id":"bffc0ef7a2edd496c2779dcb944f05488820b5e1"},{"author":{"_account_id":32240,"name":"Yadnesh Kulkarni","email":"yadnesh_kulkarni@proton.me","username":"ykulkarn"},"change_message_id":"4afa973424dc9c01e609e7ab1898b3936739f0c8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e5efef56_ac3271e0","updated":"2023-04-14 07:24:55.000000000","message":"recheck \n\nFailure doesn\u0027t seem related to the changes\n```\n2023-04-13 14:41:29.305592 | controller | telemetry_tempest_plugin.aodh.api.test_alarming_api_negative.TelemetryAlarmingNegativeTest.test_get_update_show_history_delete_deleted_alarm[id-ef45000d-0a72-4781-866d-4cb7bf2582ae,negative]\n.\n.\n2023-04-13 14:41:29.306161 | controller |     tempest.lib.exceptions.UnexpectedResponseCode: Unexpected response code received\n2023-04-13 14:41:29.306171 | controller | Details: 503\n```","commit_id":"bffc0ef7a2edd496c2779dcb944f05488820b5e1"},{"author":{"_account_id":32240,"name":"Yadnesh Kulkarni","email":"yadnesh_kulkarni@proton.me","username":"ykulkarn"},"change_message_id":"0e3034c4afba4dda752c28eed227e64edafb4f27","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"f8bda253_fd987987","updated":"2023-04-14 15:18:31.000000000","message":"recheck - telemetry-dsvm-integration-centos-9s timed out","commit_id":"bffc0ef7a2edd496c2779dcb944f05488820b5e1"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"3c810ff6544a6a7f5485397b6e68de2015f5be73","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"3966e9f7_c8badb52","in_reply_to":"238b979c_f5a03f85","updated":"2023-03-17 08:18:25.000000000","message":"This change does not change the default behavior which is quite good.\nMy main concern with upgrade still stands. Probably that can be eased by creating a new release with these new features but I\u0027m not too sure ?\n\nIf you nominate Telemetry to the projects following the stable policy then \"New features\" are clearly prohibited for backport, unless it is required to fix severe bug.\n\nBut again this all depends on the project\u0027s decision and I won\u0027t block this. I\u0027m leaving -1 to make you aware this is not what we usually do for core projects.","commit_id":"bffc0ef7a2edd496c2779dcb944f05488820b5e1"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"6378cc1d229efb0856e1fafb3318f0c3c7cbdc01","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"e42af164_58de8504","in_reply_to":"34bd7b83_9e2f48fa","updated":"2023-03-17 07:35:36.000000000","message":"I\u0027m not too much concerned with the zed backport because Antelope should include this feature so any update path should not cause the parameter is \"removed\".\n\nHowever the situation is a bit different in yoga so in case any user gets the new yoga release with this feature installed and then update their deployment to zed GA then the parameter is suddenly ignored.\n\nIn case we need this feature in downstream then I\u0027d probably suggest downstream-only backport but again it\u0027s all up to the decision in Telemetry team and there is not clear official blocker since Telemetry does not follow stable policies for some reason.","commit_id":"bffc0ef7a2edd496c2779dcb944f05488820b5e1"},{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"e3761c1a16409033f6380115f26f7d4f8834181c","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"daa8bd46_fef04b29","in_reply_to":"e5efef56_ac3271e0","updated":"2023-04-14 08:50:42.000000000","message":"good catch!\n\nGrenade is testing upgrades :/","commit_id":"bffc0ef7a2edd496c2779dcb944f05488820b5e1"},{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"5ba1c30540d9f85d99514c78c4974b9c77edb903","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"4b217dba_c9746e84","updated":"2023-04-18 05:02:36.000000000","message":"No code changes between version 1 and version 2, little changes in the commit message. Still looks good.","commit_id":"c6f00257d4586eebfcaf4a208824f5be3a63c3f4"}]}