)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"4d22a7a11beddaad789865df5fd3ac857b42452c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7850f6b4_0bc6d8d8","updated":"2024-02-12 20:56:27.000000000","message":"Can we mark them inactive after C-2? Seems like this is mostly effective 2024.2 unless we special case them, right?","commit_id":"6ee81a47851b04aa459433d0661775a5ad4c00b2"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"f5fae7aa32200e21247935db6e8bb01f425ead5e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7687eb68_2a4974d0","in_reply_to":"7850f6b4_0bc6d8d8","updated":"2024-02-12 21:02:28.000000000","message":"yeah, that is something we did not do yet or at least our Inactive project process does not cover this case. But as their gate is broken and other situation I do not think it make sense to release them for 2024.1 and say Inactive from 2024.2.\n\nI think we should add this case in process doc first and then mark it Inactive in 2024.1 itself. I will propose the process change and we can see how it looks like.","commit_id":"6ee81a47851b04aa459433d0661775a5ad4c00b2"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"b2cc3b473f334ad6f43293e57bab2394beeeeb05","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"472c5151_2c849458","updated":"2024-02-28 17:06:36.000000000","message":"As I mentioned in #openstack-tc yesterday, I\u0027m still in favor of this, especially because of the inactivity around assessing/fixing a possible vulnerability. Given that there seems to be some hesitation around approving the current parent patch [0], my preference is that the general change in [0] be discussed with the releases team at the PTG before that change is merged.  To handle this specific murano case for the 2024.1 (Caracal) release (that is, right now), I suggest that this here patch be rebased on [1], which is a special-purpose resolution recognizing that we are past the normal M-2 deadline for excluding projects from the release, but that the TC nonetheless wants to exclude murano from the 2024.1 release.  This will allow more discussion over what the general policy will be while at the same time will allow this (IMO, important) patch to be merged.\n\n[0] https://review.opendev.org/c/openstack/governance/+/908880\n[1] https://review.opendev.org/c/openstack/governance/+/910434","commit_id":"7465c5b8fbef00afa345057bf37d5dbd03fe71b1"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"3d546f42dd861ffdd6aebbf6a3538cbdbc49b6ce","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"c0b4d42d_c63dcd34","updated":"2024-02-19 07:33:38.000000000","message":"I was going to propose the same due to inactivity regarding release patches, see https://review.opendev.org/c/openstack/releases/+/906586 https://review.opendev.org/c/openstack/releases/+/903221 https://review.opendev.org/c/openstack/releases/+/903313","commit_id":"7465c5b8fbef00afa345057bf37d5dbd03fe71b1"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"a80171673ec82302dead6dd39419706908a71e0c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"39df26a1_71d20210","updated":"2024-02-13 18:34:11.000000000","message":"Not replying to VMT is especially bad.  Looks like the project is definitely inactive.","commit_id":"7465c5b8fbef00afa345057bf37d5dbd03fe71b1"},{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"d6aff5d12262053aeae84cc096a558c7d767cd31","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":3,"id":"a30aa24e_45910928","updated":"2024-02-23 21:44:24.000000000","message":"This will need to be rebased if it\u0027s to land without changing the policy. I suggest we do that.","commit_id":"7465c5b8fbef00afa345057bf37d5dbd03fe71b1"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"bd9720e8577d0c1458eec9aed0be899b094993d7","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"72f8fd09_e1165be4","in_reply_to":"472c5151_2c849458","updated":"2024-03-05 17:54:26.000000000","message":"done","commit_id":"7465c5b8fbef00afa345057bf37d5dbd03fe71b1"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"52b16b225db61fa66a39964247f4e79b0b530c64","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"082c6b8f_61412c56","updated":"2024-03-05 17:54:02.000000000","message":"rebased on top of the TC resolution for Murano","commit_id":"7120634d6e11d03d4f29bbb74ef7ae15ef10577c"}],"reference/emerging-technology-and-inactive-projects.rst":[{"author":{"_account_id":10342,"name":"Jay Faulkner","display_name":"JayF","email":"jay@jvf.cc","username":"JayF","status":"youtube.com/@oss-gr / podcast.gr-oss.io"},"change_message_id":"7e85b608a86bda20f5fc7fbcf83f6875c0aee724","unresolved":true,"context_lines":[{"line_number":86,"context_line":"``active`` during the next cycle after the cycle they entered the ``inactive``"},{"line_number":87,"context_line":"state, the TC will discuss with the team if project will be retired before the"},{"line_number":88,"context_line":"release milestone-2 of the cycle. In such a case there will be no new releases"},{"line_number":89,"context_line":"of that project."},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"Tracking"},{"line_number":92,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"6eef93f7_3b2c9250","line":89,"updated":"2024-02-13 03:59:40.000000000","message":"I suggest we add a clause here that a project can be marked inactive later in the cycle and removed from the release when there is significant evidence of inactivity, such as unresolved security vulnerabilities or gate issues which impact its ability to be released. This will make it 100% clear we can mark Murano inactive and exclude it from the release late.","commit_id":"6ee81a47851b04aa459433d0661775a5ad4c00b2"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"681386d499e78b86dddc9b3d0ddfce0373fdfc3e","unresolved":false,"context_lines":[{"line_number":86,"context_line":"``active`` during the next cycle after the cycle they entered the ``inactive``"},{"line_number":87,"context_line":"state, the TC will discuss with the team if project will be retired before the"},{"line_number":88,"context_line":"release milestone-2 of the cycle. In such a case there will be no new releases"},{"line_number":89,"context_line":"of that project."},{"line_number":90,"context_line":""},{"line_number":91,"context_line":"Tracking"},{"line_number":92,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":1,"id":"7995f179_98d3f36e","line":89,"in_reply_to":"6eef93f7_3b2c9250","updated":"2024-02-13 05:33:53.000000000","message":"Done, https://review.opendev.org/c/openstack/governance/+/908880","commit_id":"6ee81a47851b04aa459433d0661775a5ad4c00b2"}]}