)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":12393,"name":"chandan kumar","display_name":"Chandan Kumar","email":"chkumar@redhat.com","username":"chkumar246"},"change_message_id":"4f75195fe0ab228ade62d7aa120c6e423bb3f325","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"16825e3c_9ddb895d","updated":"2026-10-12 14:17:04.000000000","message":"Overall it looks, there are multiple reference of https://launchpad.net/cyborg-tempest-plugin , it does not exists. Before merging this patch, can we create this url in the launchpad?","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"5c419e18e4e3abb1df6c1d987e55ecae89e611dc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"d126a299_efec2f83","updated":"2026-10-12 13:06:53.000000000","message":"Sean asked me to take a look at this. I think it mostly makes sense. My only concern is that a good chunk of this information is regurgitating what is already provided in the project config guide. That\u0027s one downside of using an LLM to write this. I suspect this would be a better document if it was written from the perspective of a diff or supplement to that guide, and focused more on the cyborg-specific aspects of contribution (e.g. the lazy consensus approach, the naming of groups, etc.). Not -1\u0027ing since none of my comments are blockers though.","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"},{"author":{"_account_id":34452,"name":"Joan Gilabert","display_name":"jgilaber","email":"jgilaber@redhat.com","username":"jgilaber"},"change_message_id":"dff4dc79c4cd20c39894c65a6b06bb681ab3dd60","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"62bafce6_4700ead8","updated":"2026-10-08 16:55:55.000000000","message":"the added document explains mostly the processes already followed and the addition of the new approvers and reviewers groups make sense to me","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"ba7d7f625cad6ca37027020e7075d45ae4b2a02c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"9e8d7720_4ffb9f5f","in_reply_to":"16825e3c_9ddb895d","updated":"2026-10-12 18:33:41.000000000","message":"i tought i did that last cycle but i guess i did not.\nwe did create it for watcher \nhttps://launchpad.net/watcher-tempest-plugin\nso that may be what im confusing it with\n\nyes i will do that before we merge.\nwe will dicuss this tomrorow in anycase","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"}],"doc/source/contributor/agentic-coding.rst":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"d07f872b79e9d7e2d483f490eb27cee6a51b4472","unresolved":true,"context_lines":[{"line_number":27,"context_line":"configuration examples. Prefer general wording such as \"contributors\" and"},{"line_number":28,"context_line":"\"readers\" when the guidance applies to everyone."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Checked-in agent skills"},{"line_number":31,"context_line":"-----------------------"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"Cyborg does not accept project-local agent skill definitions checked into the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"a096e321_08be3c9d","line":30,"updated":"2026-10-09 14:40:18.000000000","message":"i might refine this later as i ment ot also incldue rule fiels and hooks as well but i will create a followup patch for that","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"}],"doc/source/contributor/commit-messages.rst":[{"author":{"_account_id":12393,"name":"chandan kumar","display_name":"Chandan Kumar","email":"chkumar@redhat.com","username":"chkumar246"},"change_message_id":"4f75195fe0ab228ade62d7aa120c6e423bb3f325","unresolved":true,"context_lines":[{"line_number":122,"context_line":"``Implements: blueprint NAME``"},{"line_number":123,"context_line":"    The change implements or partially implements the named blueprint."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Cyborg does not use ``DocImpact``, ``APIImpact``, ``UpgradeImpact``, or other"},{"line_number":126,"context_line":"``*Impact`` commit-message markers. Include required documentation and release"},{"line_number":127,"context_line":"notes with the implementation, based on the behavior and impact of the change."},{"line_number":128,"context_line":"See :doc:`/contributor/releasenotes` for release-note guidance."},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"Amending commits"},{"line_number":131,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"b81e42f9_d6e85d2e","line":128,"range":{"start_line":125,"start_character":0,"end_line":128,"end_character":63},"updated":"2026-10-12 14:17:04.000000000","message":"thanks for documenting that. I was using UpgradeImpact in my nvme series. Need to udpate the nvme series.","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"ba7d7f625cad6ca37027020e7075d45ae4b2a02c","unresolved":true,"context_lines":[{"line_number":122,"context_line":"``Implements: blueprint NAME``"},{"line_number":123,"context_line":"    The change implements or partially implements the named blueprint."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Cyborg does not use ``DocImpact``, ``APIImpact``, ``UpgradeImpact``, or other"},{"line_number":126,"context_line":"``*Impact`` commit-message markers. Include required documentation and release"},{"line_number":127,"context_line":"notes with the implementation, based on the behavior and impact of the change."},{"line_number":128,"context_line":"See :doc:`/contributor/releasenotes` for release-note guidance."},{"line_number":129,"context_line":""},{"line_number":130,"context_line":"Amending commits"},{"line_number":131,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"8dad7eeb_eae7e9e5","line":128,"range":{"start_line":125,"start_character":0,"end_line":128,"end_character":63},"in_reply_to":"b81e42f9_d6e85d2e","updated":"2026-10-12 18:33:41.000000000","message":"so its not a hard rule that you cant use them\n\nbut all of the automation that use to automaticlly file bugs for docs based on these git tag has been shutdown for years.\n\nwhen you added UpgradeImpact in the distant past it used to create a bug on the upgrade guide to update the doc.\n\nmost if not all of that went away when the docs were moved in tree.","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"}],"doc/source/contributor/contributing.rst":[{"author":{"_account_id":9976,"name":"Ronelle Landy","email":"rlandy@redhat.com","username":"rlandy"},"change_message_id":"172bddd35ed3ecb96f4cd2c040311cd262cdba35","unresolved":true,"context_lines":[{"line_number":77,"context_line":"Getting Your Patch Merged"},{"line_number":78,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"Changes must pass the required Zuul checks and receive ``Code-Review +2``"},{"line_number":81,"context_line":"and ``Workflow +1`` from maintainers authorized for the repository and branch."},{"line_number":82,"context_line":"Independent review is encouraged; one authorized approver may provide both"},{"line_number":83,"context_line":"votes."}],"source_content_type":"text/x-rst","patch_set":2,"id":"0d9c6aae_2c0f7d86","line":80,"updated":"2026-10-06 12:52:44.000000000","message":"iiuc, this means:\nChanges must pass the required zuul checks and receive ONE/A ``Code-Review +2`` and ONE/A ``workflow +1`` from a/any maintainer authorized ...\n\nthe switch here is from 2 +2\u0027s to one +2 and one w+1.","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"d07f872b79e9d7e2d483f490eb27cee6a51b4472","unresolved":true,"context_lines":[{"line_number":77,"context_line":"Getting Your Patch Merged"},{"line_number":78,"context_line":"~~~~~~~~~~~~~~~~~~~~~~~~~"},{"line_number":79,"context_line":""},{"line_number":80,"context_line":"Changes must pass the required Zuul checks and receive ``Code-Review +2``"},{"line_number":81,"context_line":"and ``Workflow +1`` from maintainers authorized for the repository and branch."},{"line_number":82,"context_line":"Independent review is encouraged; one authorized approver may provide both"},{"line_number":83,"context_line":"votes."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3f05e0ec_19626ee6","line":80,"in_reply_to":"0d9c6aae_2c0f7d86","updated":"2026-10-09 14:40:18.000000000","message":"not quite i intentionally did not want to encode the details in this high level summary as i wanted the authoritative info to live in the new doc.\n\nmechanically merging a patch alwasy requried a signle +2 and +w form a ci configuration perspective. any waitign for a second +2 was alwasy a convention not an tool enforcement so removed the references form this short summary as they really should not be duplicated here.","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"}],"doc/source/contributor/maintainers-guide.rst":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"5c419e18e4e3abb1df6c1d987e55ecae89e611dc","unresolved":true,"context_lines":[{"line_number":7,"context_line":"This guide describes how Cyborg delegates review and approval responsibility,"},{"line_number":8,"context_line":"how maintainers make decisions, and how contributors can get changes reviewed."},{"line_number":9,"context_line":"It also records the Launchpad groups used to administer Cyborg\u0027s bug trackers."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"OpenStack traditionally uses ``core reviewer`` or ``core team`` for people who"},{"line_number":12,"context_line":"maintain a project. This guide uses ``maintainer`` more broadly. A project is"},{"line_number":13,"context_line":"maintained by everyone who reviews changes, reports and triages bugs, improves"},{"line_number":14,"context_line":"documentation, tests releases, or otherwise contributes to its health. Gerrit"},{"line_number":15,"context_line":"group membership grants specific permissions; it does not define the limits of"}],"source_content_type":"text/x-rst","patch_set":2,"id":"499bb1e9_87af9495","line":12,"range":{"start_line":10,"start_character":1,"end_line":12,"end_character":77},"updated":"2026-10-12 13:06:53.000000000","message":"nit: You probably want to format these as *emphasis* rather than `literal`?\n\n```suggestion\n\nOpenStack traditionally uses *core reviewer* or *core team* for people who\nmaintain a project. This guide uses *maintainer* more broadly. A project is\n```","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"ba7d7f625cad6ca37027020e7075d45ae4b2a02c","unresolved":true,"context_lines":[{"line_number":7,"context_line":"This guide describes how Cyborg delegates review and approval responsibility,"},{"line_number":8,"context_line":"how maintainers make decisions, and how contributors can get changes reviewed."},{"line_number":9,"context_line":"It also records the Launchpad groups used to administer Cyborg\u0027s bug trackers."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"OpenStack traditionally uses ``core reviewer`` or ``core team`` for people who"},{"line_number":12,"context_line":"maintain a project. This guide uses ``maintainer`` more broadly. A project is"},{"line_number":13,"context_line":"maintained by everyone who reviews changes, reports and triages bugs, improves"},{"line_number":14,"context_line":"documentation, tests releases, or otherwise contributes to its health. Gerrit"},{"line_number":15,"context_line":"group membership grants specific permissions; it does not define the limits of"}],"source_content_type":"text/x-rst","patch_set":2,"id":"b4d5bed6_2f8099db","line":12,"range":{"start_line":10,"start_character":1,"end_line":12,"end_character":77},"in_reply_to":"499bb1e9_87af9495","updated":"2026-10-12 18:33:41.000000000","message":"no i  wanted to use litral\n\ni could use * i guess because that at least does not use italics.\nbut i prefer litrilas.\n\nit should render the same in our theme more or less.\n\nill compare this locally and see how it looks.","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"5c419e18e4e3abb1df6c1d987e55ecae89e611dc","unresolved":true,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Governance and principles"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Cyborg uses the OpenStack Project Team Lead (PTL) governance model. The current"},{"line_number":22,"context_line":"PTL and project liaisons are listed on the `Cyborg governance page`_. Cyborg"},{"line_number":23,"context_line":"may adopt the OpenStack distributed leadership model in the future without"},{"line_number":24,"context_line":"changing the delegation principles in this guide."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":".. _`Cyborg governance page`: https://governance.openstack.org/tc/reference/projects/cyborg.html"},{"line_number":27,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"6900ffda_6196faac","line":24,"range":{"start_line":20,"start_character":1,"end_line":24,"end_character":49},"updated":"2026-10-12 13:06:53.000000000","message":"Unless you plan to adopt DPL in the near-term, I\u0027d drop this. It\u0027s just speculation and doesn\u0027t add anything here.\n\n```suggestion\n\nCyborg uses the OpenStack Project Team Lead (PTL) governance model. The current\nPTL and project liaisons are listed on the `Cyborg governance page`_.\n```","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"ba7d7f625cad6ca37027020e7075d45ae4b2a02c","unresolved":true,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Governance and principles"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"Cyborg uses the OpenStack Project Team Lead (PTL) governance model. The current"},{"line_number":22,"context_line":"PTL and project liaisons are listed on the `Cyborg governance page`_. Cyborg"},{"line_number":23,"context_line":"may adopt the OpenStack distributed leadership model in the future without"},{"line_number":24,"context_line":"changing the delegation principles in this guide."},{"line_number":25,"context_line":""},{"line_number":26,"context_line":".. _`Cyborg governance page`: https://governance.openstack.org/tc/reference/projects/cyborg.html"},{"line_number":27,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fcce84df_ae315090","line":24,"range":{"start_line":20,"start_character":1,"end_line":24,"end_character":49},"in_reply_to":"6900ffda_6196faac","updated":"2026-10-12 18:33:41.000000000","message":"we had, it will be a topic at the ptg.\noriginally that was the plan for last cycle but we missed the window for reasons.\nthis cycle i have kept the PTL next cycle im unsure if i will continue or look to move to DPL before the new cycle.","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"5c419e18e4e3abb1df6c1d987e55ecae89e611dc","unresolved":true,"context_lines":[{"line_number":67,"context_line":"Group membership, rather than this document, is the authoritative roster."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":".. _`Cyborg Gerrit groups`: https://review.opendev.org/admin/groups/q/filter:cyborg"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"``cyborg-core``"},{"line_number":72,"context_line":"---------------"},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"``cyborg-core`` is the project-wide maintainer group. Its members have"},{"line_number":75,"context_line":"``Code-Review -2..+2`` and ``Workflow -1..+1`` on maintained branches of all"},{"line_number":76,"context_line":"official Cyborg deliverables:"},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"* ``cyborg``"},{"line_number":79,"context_line":"* ``python-cyborgclient``"},{"line_number":80,"context_line":"* ``cyborg-specs``"},{"line_number":81,"context_line":"* ``cyborg-tempest-plugin``"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Core maintainers are expected to understand how changes across these"},{"line_number":84,"context_line":"repositories affect Cyborg\u0027s design, compatibility, testing, releases, and"},{"line_number":85,"context_line":"long-term maintenance. Core permissions may be granted directly or through"},{"line_number":86,"context_line":"inclusion in the scoped groups below; in either case, ``cyborg-core`` retains"},{"line_number":87,"context_line":"the project-wide rights described here. The narrower groups allow contributors"},{"line_number":88,"context_line":"to assume responsibility without first taking on this project-wide scope."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"``cyborg-approvers``"},{"line_number":91,"context_line":"--------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"cb00462f_10158481","line":88,"range":{"start_line":70,"start_character":1,"end_line":88,"end_character":73},"updated":"2026-10-12 13:06:53.000000000","message":"Is there a reason to keep `cyborg-core` around long-term, given the overlap with `cyborg-approvers`? Context: https://review.opendev.org/c/openstack/project-config/+/1003840","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"},{"author":{"_account_id":12393,"name":"chandan kumar","display_name":"Chandan Kumar","email":"chkumar@redhat.com","username":"chkumar246"},"change_message_id":"4f75195fe0ab228ade62d7aa120c6e423bb3f325","unresolved":true,"context_lines":[{"line_number":142,"context_line":"``Workflow -1..+1``. The approver group is included in the reviewer group."},{"line_number":143,"context_line":"Both groups are scoped to ``cyborg-tempest-plugin`` only."},{"line_number":144,"context_line":""},{"line_number":145,"context_line":"On maintained stable branches, membership in ``cyborg-tempest-reviewers``"},{"line_number":146,"context_line":"grants both ``Code-Review -2..+2`` and ``Workflow -1..+1``. Membership in"},{"line_number":147,"context_line":"``cyborg-tempest-approvers`` is not required to approve stable-branch changes."},{"line_number":148,"context_line":"Members of the Tempest core team are included in both plugin groups. This lets"},{"line_number":149,"context_line":"Tempest maintainers keep the plugin aligned with Tempest interfaces and"},{"line_number":150,"context_line":"policies without granting them rights on unrelated Cyborg repositories."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"Launchpad administration"},{"line_number":153,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"f70ac948_77cb8879","line":150,"range":{"start_line":145,"start_character":0,"end_line":150,"end_character":71},"updated":"2026-10-12 14:17:04.000000000","message":"Tempest is branchless, It does not have stable branches. I think we can drop this section.","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"},{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"ba7d7f625cad6ca37027020e7075d45ae4b2a02c","unresolved":true,"context_lines":[{"line_number":142,"context_line":"``Workflow -1..+1``. The approver group is included in the reviewer group."},{"line_number":143,"context_line":"Both groups are scoped to ``cyborg-tempest-plugin`` only."},{"line_number":144,"context_line":""},{"line_number":145,"context_line":"On maintained stable branches, membership in ``cyborg-tempest-reviewers``"},{"line_number":146,"context_line":"grants both ``Code-Review -2..+2`` and ``Workflow -1..+1``. Membership in"},{"line_number":147,"context_line":"``cyborg-tempest-approvers`` is not required to approve stable-branch changes."},{"line_number":148,"context_line":"Members of the Tempest core team are included in both plugin groups. This lets"},{"line_number":149,"context_line":"Tempest maintainers keep the plugin aligned with Tempest interfaces and"},{"line_number":150,"context_line":"policies without granting them rights on unrelated Cyborg repositories."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"Launchpad administration"},{"line_number":153,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":2,"id":"cf14a831_73ca50ec","line":150,"range":{"start_line":145,"start_character":0,"end_line":150,"end_character":71},"in_reply_to":"f70ac948_77cb8879","updated":"2026-10-12 18:33:41.000000000","message":"oh you are right i was overthingink that yes i can simplfy it.","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"},{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"5c419e18e4e3abb1df6c1d987e55ecae89e611dc","unresolved":true,"context_lines":[{"line_number":307,"context_line":"#. answer questions and resolve substantive objections; and"},{"line_number":308,"context_line":"#. reconsider the waiting period after any substantial revision."},{"line_number":309,"context_line":""},{"line_number":310,"context_line":"After requesting feedback, an approver should generally allow 3 to 30 days for"},{"line_number":311,"context_line":"responses. The approver should select a period within that range based on"},{"line_number":312,"context_line":"complexity, impact, reversibility, test coverage, and proximity to a release"},{"line_number":313,"context_line":"milestone. Silence is not a substitute for"}],"source_content_type":"text/x-rst","patch_set":2,"id":"945cd693_c35a3f25","line":310,"updated":"2026-10-12 13:06:53.000000000","message":"I\u0027d move this up to point 2 above. My first question on reading this was \"what is a \"reasonable period\"\n\nNote that what you\u0027re describing here sounds like lazy consensus. Maybe mention that term?","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"}],"doc/source/contributor/release-guide.rst":[{"author":{"_account_id":12393,"name":"chandan kumar","display_name":"Chandan Kumar","email":"chkumar@redhat.com","username":"chkumar246"},"change_message_id":"4f75195fe0ab228ade62d7aa120c6e423bb3f325","unresolved":true,"context_lines":[{"line_number":99,"context_line":"Python Cyborg Client Launchpad"},{"line_number":100,"context_line":"    `Client library tracking \u003chttps://launchpad.net/python-cyborgclient\u003e`__"},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Cyborg Tempest Plugin Launchpad"},{"line_number":103,"context_line":"    `Test plugin tracking \u003chttps://launchpad.net/cyborg-tempest-plugin\u003e`__"},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"Project Team Gathering"},{"line_number":106,"context_line":"----------------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"38eaa8f4_a70b0bea","line":103,"range":{"start_line":102,"start_character":0,"end_line":103,"end_character":74},"updated":"2026-10-12 14:17:04.000000000","message":"https://launchpad.net/cyborg-tempest-plugin does not exists. We can drop this one or recreate that project in launchpad.","commit_id":"3cdb5cc25a142140ed88d9fdd33ff8eac932b940"}]}