From 8224a42b0aa251033a58ec32eaf0d3a3094702da Mon Sep 17 00:00:00 2001 From: Myles Penner Date: Fri, 28 Nov 2025 07:35:07 -0800 Subject: [PATCH] fix: Fix broken MIR bug list URL The ampersands in the link caused it to not render properly in the address bar. Using a tag was advised as the preffered workaround to this common Sphinx problem. --- docs/MIR/mir-roles-and-steps.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/MIR/mir-roles-and-steps.md b/docs/MIR/mir-roles-and-steps.md index 1d6060d4..95d9c3b8 100644 --- a/docs/MIR/mir-roles-and-steps.md +++ b/docs/MIR/mir-roles-and-steps.md @@ -60,7 +60,7 @@ File a bug report about the package, titled "`[MIR] sourcepackagename`". Subscribe [`ubuntu-mir`](https://launchpad.net/~ubuntu-mir) to the bug report. Keep it in state "NEW" and do not assign it to anyone: this ensures that it appears in the -[MIR bug list](https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-date_last_updated&field.status%3Alist=NEW&assignee_option=none&field.assignee=&field.subscriber=ubuntu-mir). +MIR bug list. (mir-step-2)= @@ -105,12 +105,12 @@ For other statuses, see the {ref}`mir-process-states` page. ### Refer back to reporter - + If, during the review process, tasks are identified that need to be completed, the bug is set to `Incomplete`. This reflects that the onus is back on the **reporter** to drive the completion of those tasks forward before more progress can be made. - + Common examples are "please add an automated test" or "this needs the new version". @@ -147,7 +147,7 @@ At this point, **Archive Admins** will promote approved packages to `main`. * If a new source package contains *only* code which is already in main (e.g. a source package split or rename, or source packages with a version in the name), it may not need a full review. - + In such cases, submitting an MIR bug with an explanation (without the full template) **or** updating/extending an existing MIR bug for the package and re-opening it by setting it to "NEW" is sufficient.