Skip to content

Commit 28c7d4e

Browse files
committed
Add 25.10 upgrade notes
1 parent 27871b5 commit 28c7d4e

File tree

2 files changed

+22
-0
lines changed

2 files changed

+22
-0
lines changed

content/admin/upgrade/index.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -101,6 +101,7 @@ of the new ejabberd version if you need to update those tables yourself manually
101101
The corresponsing ugprade notes are available in the release notes of each release,
102102
and also available in the [Archive](../../archive/index.md) section:
103103

104+
- [Upgrading from ejabberd 25.08 to 25.10](../../archive/25.10/upgrade.md)
104105
- [Upgrading from ejabberd 25.07 to 25.08](../../archive/25.08/upgrade.md)
105106
- [Upgrading from ejabberd 25.04 to 25.07](../../archive/25.07/upgrade.md)
106107
- [Upgrading from ejabberd 25.03 to 25.04](../../archive/25.04/upgrade.md)

content/archive/25.10/upgrade.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# Upgrade to ejabberd 25.10
2+
3+
If you upgrade ejabberd from a previous release to [25.10](../../archive/25.10/index.md),
4+
there are no mandatory changes in SQL schemas, configuration, API commands or hooks.
5+
6+
But if you are using the new SQL schema, it's recommended to update your setup
7+
to use the new arguments and option:
8+
9+
When preparing configuration, replace the previous argument with the current argument:
10+
11+
```
12+
./configure --enable-new-sql-schema
13+
./configure --enable-multihost-sql-schema
14+
```
15+
16+
When configuring ejabberd, replace the previous option with the current option:
17+
18+
```
19+
new_sql_schema: true
20+
sql_schema_multihost: true
21+
```

0 commit comments

Comments
 (0)