diff options
Diffstat (limited to 'doc/release_notes_3.0.0.txt')
| -rw-r--r-- | doc/release_notes_3.0.0.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/release_notes_3.0.0.txt b/doc/release_notes_3.0.0.txt index e33cfcbe0..644efb1bc 100644 --- a/doc/release_notes_3.0.0.txt +++ b/doc/release_notes_3.0.0.txt @@ -9,7 +9,7 @@ * The database schema may change before ejabberd 3.0.0 is released, * and no migration code will be developed for this preliminary schema. * The only supported migrations are -* from any ejabberd 0.9.0 ... 2.1.5 to the final 3.0.0. +* from any ejabberd 0.9.0 ... 2.1.x to the final 3.0.0. * Don't use this preliminary ejabberd release for a production server. * You can test this release with a blank database or with a copy of your * production database, but don't let your users connect to this copy @@ -45,15 +45,15 @@ ejabberd 3.0.0 includes three major changes: but it is still incomplete, untested and undocumented. -This is a more detailed list of changes since ejabberd 2.1.5: +This is a more detailed list of changes since ejabberd 2.1.x releases: * Requirements - Erlang/OTP R12B-5 or higher is required -- exmpp 0.9.5 or higher is required, not optional +- exmpp 0.9.6 or higher is required, not optional - ESASL library is optional, for SASL GSSAPI authentication - Libexpat not required by ejabberd, it uses exmpp now (EJAB-1111) - GNU Iconv not required, because mod_irc isn't included anymore (EJAB-954) -- Only database migration from ejabberd 0.9.0 up to 2.1.5 is supported +- Only database migration from ejabberd 0.9.0 up to 2.1.x is supported - ejabberd modules developed for previous releases need to be upgraded to exmpp * Configuration |