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

@@ -27,7 +27,7 @@ Unstable release planning
At the start of a development cycle, milestones are created for each release in
the cycle according to the [GNOME release
schedule](https://wiki.gnome.org/Schedule). GLib roughly follows the GNOME
schedule](https://release.gnome.org/calendar/). GLib roughly follows the GNOME
release schedule, but makes its releases one or two weeks ahead of each
corresponding GNOME release. This allows other GNOME modules to depend on the
correct GLib version for new APIs. GLib does not follow the GNOME module
@@ -42,7 +42,7 @@ maintainers think will have a wide benefit are prioritised.
As a development cycle progresses, some of the releases are timed to coincide
with [GNOMEs API/feature, string and hard code
freezes](https://wiki.gnome.org/ReleasePlanning/Freezes). Issues which add API
freezes](https://handbook.gnome.org/release-planning/freezes.html). Issues which add API
and features are scheduled for the earlier micro releases in a development
cycle, followed by issues which add or change translatable strings, followed by
smaller bug fixes, documentation and unit test updates.