docs: Update various outdated links which pointed to wiki.gnome.org

wiki.gnome.org has been retired but for some reason none of the old
pages were given HTTP redirects, so everyone has to update all their
links manually everywhere.

Signed-off-by: Philip Withnall <pwithnall@gnome.org>
This commit is contained in:
Philip Withnall
2025-01-23 14:00:46 +00:00
parent d11dac3836
commit 9e3c017df8
6 changed files with 11 additions and 11 deletions

View File

@@ -88,7 +88,7 @@ Several labels are worth highlighting:
as confidential.
* Merge After Freeze: Merge requests which have been accepted, but which cant
be merged yet as GLib is in
[code freeze](https://wiki.gnome.org/ReleasePlanning/Freezes). All MRs tagged
[code freeze](https://handbook.gnome.org/release-planning/freezes.html). All MRs tagged
like this will be merged en-masse when the freeze ends.
* Needs Information: Issues which are blocked due to needing more information
from the reporter. These can be closed after 4 weeks if the reporter does not
@@ -105,10 +105,10 @@ Several labels are worth highlighting:
the translation team to be looped into an issue or merge request.
* API deprecation: Issues or merge requests which deprecate GLib API, and hence
can only land in an unstable release outside an
[API freeze](https://wiki.gnome.org/ReleasePlanning/Freezes).
[API freeze](https://handbook.gnome.org/release-planning/freezes.html#api-abi-freeze).
* New API: Issues or merge requests which add new GLib API, and hence can only
land in an unstable release outside an
[API freeze](https://wiki.gnome.org/ReleasePlanning/Freezes).
[API freeze](https://handbook.gnome.org/release-planning/freezes.html#api-abi-freeze).
* Intermittent: Issues (such as test failures) which can only be reproduced
intermittently.
* Test failure: Issues which revolve around a unit test failing. Typically