mirror of
https://github.com/element-hq/synapse
synced 2024-08-18 21:30:54 +00:00
deploy: 5427cc20b9
This commit is contained in:
parent
5f23acdbfe
commit
cf038bdab8
2 changed files with 4 additions and 4 deletions
|
@ -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>
|
||||
|
||||
|
|
|
@ -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
|
||||
|
|
Loading…
Reference in a new issue