Skip to content

Commit 8fceb3e

Browse files
committed
Add notes for 23.01 upgrade
1 parent 8a52027 commit 8fceb3e

File tree

2 files changed

+20
-0
lines changed

2 files changed

+20
-0
lines changed
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
title: Upgrade to ejabberd 23.01
3+
toc: true
4+
---
5+
6+
There is a new module, new hooks, new options, and some option accepts additional values,
7+
but there are no breaking changes in SQL schemas, configuration, or commands API.
8+
9+
Please check the ejabberd [23.01](/archive/23_01/) release announcement for details
10+
about the improvements.
11+
12+
## Changes in option `outgoing_s2s_families`
13+
14+
The `outgoing_s2s_families` top-level option specifies which address families to try, in what order.
15+
16+
The default value has now been changed to try IPv6 first, as servers are within data centers where IPv6 is more commonly enabled (contrary to clients). And if it’s not present, then it’ll just fall back to IPv4.
17+
18+
By the way, this option is obsolete and irrelevant when using ejabberd 23.01 and Erlang/OTP 22, or newer versions of them.
19+

content/admin/upgrade/index.md

+1
Original file line numberDiff line numberDiff line change
@@ -95,6 +95,7 @@ of the new ejabberd version if you need to update those tables yourself manually
9595

9696
# Specific version upgrade notes
9797

98+
- [Upgrading from ejabberd 22.10 to 23.01](/admin/upgrade/from_22.10_to_23.01/)
9899
- [Upgrading from ejabberd 22.05 to 22.10](/admin/upgrade/from_22.05_to_22.10/)
99100
- [Upgrading from ejabberd 21.12 to 22.05](/admin/upgrade/from_21.12_to_22.05/)
100101
- [Upgrading from ejabberd 21.07 to 21.12](/admin/upgrade/from_21.07_to_21.12/)

0 commit comments

Comments
 (0)