Skip to contentSkip to conversation

Update documentation to refer to new location for issues

PATCH In review Stefan Weil 4 participants 5 messages Jun 19, 2021 – Jun 23, 2021

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Update documentation to refer to new location for issues

---

Another update is needed for scripts/show-fixed-bugs.sh.

Stefan

 .github/lockdown.yml | 6 +++---
 README.rst           | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)
.github/lockdown.yml +3 -3
index 07fc2f31ee..d3546bd2bc 100644
@@ -14,11 +14,11 @@ issues:
     at https://gitlab.com/qemu-project/qemu.git.
     The project does not process issues filed on GitHub.
 
-    The project issues are tracked on Launchpad:
-    https://bugs.launchpad.net/qemu
+    The project issues are tracked on GitLab:
+    https://gitlab.com/qemu-project/qemu/-/issues
 
     QEMU welcomes bug report contributions. You can file new ones on:
-    https://bugs.launchpad.net/qemu/+filebug
+    https://gitlab.com/qemu-project/qemu/-/issues/new
 
 pulls:
   comment: |
README.rst +3 -3
index a92c7394b7..79b19f1481 100644
@@ -131,16 +131,16 @@ will be tagged as my-feature-v2.
 Bug reporting
 =============
 
-The QEMU project uses Launchpad as its primary upstream bug tracker. Bugs
+The QEMU project uses GitLab issues to track bugs. Bugs
 found when running code built from QEMU git or upstream released sources
 should be reported via:
 
-* `<https://bugs.launchpad.net/qemu/>`_
+* `<https://gitlab.com/qemu-project/qemu/-/issues>`_
 
 If using QEMU via an operating system vendor pre-built binary package, it
 is preferable to report bugs to the vendor's own bug tracker first. If
 the bug is also known to affect latest upstream code, it can also be
-reported via launchpad.
+reported via GitLab.
 
 For additional information on bug reporting consult:
 
Signature · 1 line
2.30.2
Reviewed-by on v1 1/1
#3 lore raw
In reply to Stefan Weil
Quoted 4 lines · Stefan Weil

---

Another update is needed for scripts/show-fixed-bugs.sh.

Don't worry about that script, I'll remove it after the next release (v6.1) has been done. The script is then hopefully not necessary anymore thanks to the possibility to close bugs automatically on commit in GitLab.

Quoted 30 lines
.github/lockdown.yml +3 -3
index 07fc2f31ee..d3546bd2bc 100644
@@ -14,11 +14,11 @@ issues:
      at https://gitlab.com/qemu-project/qemu.git.
      The project does not process issues filed on GitHub.
 
-    The project issues are tracked on Launchpad:
-    https://bugs.launchpad.net/qemu
+    The project issues are tracked on GitLab:
+    https://gitlab.com/qemu-project/qemu/-/issues
 
      QEMU welcomes bug report contributions. You can file new ones on:
-    https://bugs.launchpad.net/qemu/+filebug
+    https://gitlab.com/qemu-project/qemu/-/issues/new
 
  pulls:
    comment: |
README.rst +1 -1
index a92c7394b7..79b19f1481 100644
@@ -131,16 +131,16 @@ will be tagged as my-feature-v2.
  Bug reporting
  =============
 
-The QEMU project uses Launchpad as its primary upstream bug tracker. Bugs
+The QEMU project uses GitLab issues to track bugs. Bugs
  found when running code built from QEMU git or upstream released sources

README.rst will be tagged as my-feature-v2. · line 143

Quoted 10 lines
README.rst +2 -2
  should be reported via:
 
-* `<https://bugs.launchpad.net/qemu/>`_
+* `<https://gitlab.com/qemu-project/qemu/-/issues>`_
 
  If using QEMU via an operating system vendor pre-built binary package, it
  is preferable to report bugs to the vendor's own bug tracker first. If
  the bug is also known to affect latest upstream code, it can also be
-reported via launchpad.
+reported via GitLab.