summary refs log tree commit diff
diff options
context:
space:
mode:
authorclokep <clokep@users.noreply.github.com>2023-08-24 15:07:07 +0000
committerclokep <clokep@users.noreply.github.com>2023-08-24 15:07:07 +0000
commitcf038bdab8421a704c9779081d8a244761c71ebf (patch)
treebd0430e7c643455b2a804c727d19796e6c4f3bdd
parentdeploy: 7064b4bcf311c45855c0f9d11a9db8a963b252b9 (diff)
downloadsynapse-cf038bdab8421a704c9779081d8a244761c71ebf.tar.xz
deploy: 5427cc20b90b7232ec678967bb04ef604923200f
-rw-r--r--develop/development/releases.html4
-rw-r--r--develop/print.html4
2 files changed, 4 insertions, 4 deletions
diff --git a/develop/development/releases.html b/develop/development/releases.html
index 5cea2ff5ec..4e96f192c1 100644
--- a/develop/development/releases.html
+++ b/develop/development/releases.html
@@ -158,7 +158,7 @@ occurring on Tuesdays:</p>
 <p>Note that this schedule might be modified depending on the availability of the
 Synapse team, e.g. releases may be skipped to avoid holidays.</p>
 <p>Release announcements can be found in the
-<a href="https://matrix.org/blog/category/releases">release category of the Matrix blog</a>.</p>
+<a href="https://matrix.org/category/releases">release category of the Matrix blog</a>.</p>
 <h2 id="bugfix-releases"><a class="header" href="#bugfix-releases">Bugfix releases</a></h2>
 <p>If a bug is found after release that is deemed severe enough (by a combination
 of the impacted users and the impact on those users) then a bugfix release may
@@ -175,7 +175,7 @@ immediately before the next release candidate. An example of this might be:</p>
 be held to be released together.</p>
 <p>In some cases, a pre-disclosure of a security release will be issued as a notice
 to Synapse operators that there is an upcoming security release. These can be
-found in the <a href="https://matrix.org/blog/category/security">security category of the Matrix blog</a>.</p>
+found in the <a href="https://matrix.org/category/security">security category of the Matrix blog</a>.</p>
 
                     </main>
 
diff --git a/develop/print.html b/develop/print.html
index 4b9e4e02f6..9bdaaf20e9 100644
--- a/develop/print.html
+++ b/develop/print.html
@@ -16648,7 +16648,7 @@ occurring on Tuesdays:</p>
 <p>Note that this schedule might be modified depending on the availability of the
 Synapse team, e.g. releases may be skipped to avoid holidays.</p>
 <p>Release announcements can be found in the
-<a href="https://matrix.org/blog/category/releases">release category of the Matrix blog</a>.</p>
+<a href="https://matrix.org/category/releases">release category of the Matrix blog</a>.</p>
 <h2 id="bugfix-releases"><a class="header" href="#bugfix-releases">Bugfix releases</a></h2>
 <p>If a bug is found after release that is deemed severe enough (by a combination
 of the impacted users and the impact on those users) then a bugfix release may
@@ -16665,7 +16665,7 @@ immediately before the next release candidate. An example of this might be:</p>
 be held to be released together.</p>
 <p>In some cases, a pre-disclosure of a security release will be issued as a notice
 to Synapse operators that there is an upcoming security release. These can be
-found in the <a href="https://matrix.org/blog/category/security">security category of the Matrix blog</a>.</p>
+found in the <a href="https://matrix.org/category/security">security category of the Matrix blog</a>.</p>
 <div style="break-before: page; page-break-before: always;"></div><h1 id="some-notes-on-how-we-use-git"><a class="header" href="#some-notes-on-how-we-use-git">Some notes on how we use git</a></h1>
 <h2 id="on-keeping-the-commit-history-clean"><a class="header" href="#on-keeping-the-commit-history-clean">On keeping the commit history clean</a></h2>
 <p>In an ideal world, our git commit history would be a linear progression of