Chapril/xmpp.chapril.org-ejabberd
24
1
Fork 0
mirror of https://github.com/processone/ejabberd.git synced 2024-06-28 22:52:27 +02:00
Code Releases Activity

Update version numbers of the related: exmpp, ejabberd 2, and Erlang

Browse Source
This commit is contained in:
Badlop 2011-03-11 10:55:34 +01:00
parent 33feca74ec
commit 8cd0894ad5
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README
View File

@ -8,7 +8,7 @@ Quickstart guide
To compile ejabberd you need: To compile ejabberd you need:
- GNU Make - GNU Make
- GCC - GCC
- Erlang/OTP R12B-5 or higher. Recommended: R12B-5 and R13B04. - Erlang/OTP R12B-5 or higher. Recommended: R12B-5, R13B04 and R14B01.
Avoid R14A and R14B. Avoid R14A and R14B.
- exmpp 0.9.6 or higher - exmpp 0.9.6 or higher
- OpenSSL 0.9.8 or higher, for STARTTLS, SASL and SSL encryption. - OpenSSL 0.9.8 or higher, for STARTTLS, SASL and SSL encryption.

2
doc/guide.tex
View File

@ -312,7 +312,7 @@ To compile \ejabberd{} on a `Unix-like' operating system, you need:
\begin{itemize} \begin{itemize}
\item GNU Make \item GNU Make
\item GCC \item GCC
\item Erlang/OTP R12B-5 or higher. The recommended versions are R12B-5 and R13B04. \item Erlang/OTP R12B-5 or higher. The recommended versions are R12B-5, R13B04 and R14B01.
Don't use R14A or R14B because \footahref{http://www.erlang.org/cgi-bin/ezmlm-cgi/4/54598}{they have a bug}. Don't use R14A or R14B because \footahref{http://www.erlang.org/cgi-bin/ezmlm-cgi/4/54598}{they have a bug}.
\item exmpp 0.9.6 or higher \item exmpp 0.9.6 or higher
\item OpenSSL 0.9.8 or higher, for STARTTLS, SASL and SSL encryption. \item OpenSSL 0.9.8 or higher, for STARTTLS, SASL and SSL encryption.

8
doc/release_notes_3.0.0.txt
View File

@ -9,7 +9,7 @@
* The database schema may change before ejabberd 3.0.0 is released, * The database schema may change before ejabberd 3.0.0 is released,
* and no migration code will be developed for this preliminary schema. * and no migration code will be developed for this preliminary schema.
* The only supported migrations are * 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. * 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 * 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 * 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. 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 * Requirements
- Erlang/OTP R12B-5 or higher is required - 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 - ESASL library is optional, for SASL GSSAPI authentication
- Libexpat not required by ejabberd, it uses exmpp now (EJAB-1111) - Libexpat not required by ejabberd, it uses exmpp now (EJAB-1111)
- GNU Iconv not required, because mod_irc isn't included anymore (EJAB-954) - 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 - ejabberd modules developed for previous releases need to be upgraded to exmpp
* Configuration * Configuration