paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-03 21:43:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

changelog: Remove broken link.

Browse Source 
Signed-off-by: Anders Kaseorg <anders@zulip.com>
This commit is contained in:
Anders Kaseorg
2022-03-30 20:02:55 -07:00
committed by Tim Abbott
parent b7f670f5a0
commit 7de1e7c477
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/overview/changelog.md
View File

@@ -1576,7 +1576,7 @@ Zulip installations; it has minimal changes for existing servers.
disruption by running this migration first, before beginning the disruption by running this migration first, before beginning the
user-facing downtime. However, if you'd like to watch the downtime user-facing downtime. However, if you'd like to watch the downtime
phase of the upgrade closely, we recommend phase of the upgrade closely, we recommend
[running them first manually](https://zulip.readthedocs.io/en/1.9.0/production/expensive-migrations.html) running them first manually
as well as the usual trick of doing an apt upgrade first. as well as the usual trick of doing an apt upgrade first.
#### Full feature changelog #### Full feature changelog
@@ -1965,7 +1965,7 @@ running a version from before 1.7 should upgrade directly to 1.7.1.
minimizes disruption by running these first, before beginning the minimizes disruption by running these first, before beginning the
user-facing downtime. However, if you'd like to watch the downtime user-facing downtime. However, if you'd like to watch the downtime
phase of the upgrade closely, we recommend phase of the upgrade closely, we recommend
[running them first manually](https://zulip.readthedocs.io/en/1.9.0/production/expensive-migrations.html) running them first manually
as well as the usual trick of doing an apt upgrade first. as well as the usual trick of doing an apt upgrade first.
- We've removed support for an uncommon legacy deployment model where - We've removed support for an uncommon legacy deployment model where