diff options
Diffstat (limited to 'doc/release_notes_1.0.0.txt')
| -rw-r--r-- | doc/release_notes_1.0.0.txt | 131 |
1 files changed, 66 insertions, 65 deletions
diff --git a/doc/release_notes_1.0.0.txt b/doc/release_notes_1.0.0.txt index ae28ab340..426ba63fa 100644 --- a/doc/release_notes_1.0.0.txt +++ b/doc/release_notes_1.0.0.txt @@ -1,112 +1,113 @@ - Release notes + Release Notes ejabberd 1.0.0 - 2005-12-13 + 14 December 2005 - This document describes the main changes in ejabberd 1.0.0. This version is - compliant with the XMPP (eXtensible Messaging and Presence Protocol) - standard. ejabberd is the first Open Source server claiming to fully - comply to the XMPP standard. + This document describes the main changes in ejabberd 1.0.0. Unique in this + version is the compliancy with the XMPP (eXtensible Messaging and Presence + Protocol) standard. ejabberd is the first Open Source Jabber server claiming + to fully comply to the XMPP standard. - The code can be downloaded from the Process-one website: + ejabberd can be downloaded from the Process-one website: http://www.process-one.net/en/projects/ejabberd/ - For more detailed information, please refer to ejabberd User Guide - on the Process-one website: + Detailed information can be found in the ejabberd Feature Sheet and User + Guide which are available on the Process-one website: http://www.process-one.net/en/projects/ejabberd/docs.html - Recent changes include.... + Recent changes include: -Encrypted server-to-server connections +Server-to-server Encryption for Enhanced Security - - Support for STARTTLS+SASL EXTERNAL for Server-to-Server connections. - - STARTTLS+Dialback has been implemented for Server-to-Server (s2s) - connections. Those options are handled with two new config file options - (s2s_use_starttls and s2s_certfile). See ejabberd.cfg.example for usage - examples. - - DNSName certificate field and DNS name matching are supported. - - Per virtual host certificate can be defined. + - Support for STARTTLS and SASL EXTERNAL to secure server-to-server traffic + has been added. + - Also, STARTTLS and Dialback has been implemented for server-to-server (s2s) + connections. Detailed information about these new features can be found on + http://ejabberd.jabber.ru/s2s-encryption + - commonName and dNSName fields matching were introduced to ease the process + of retrieving certificates. + - Different certificates can be defined for each virtual host. ODBC Support - ODBC support has been improved to allow production use of ejabberd with relational databases. - - Support for VCard storage in ODBC has been added. - - ejd2odbc.erl: is a program that convert an installation from Erlang Mnesia - database to an ODBC relational database. + - Support for vCard storage in ODBC has been added. + - ejd2odbc.erl is a tool to convert an installation from Erlang's database + Mnesia to an ODBC compatible relational database. -Native PostgreSQL support +Native PostgreSQL Support - - Native postgreSQL support has been added: You can now use a PostgreSQL - database without the need to go through the ODBC driver. + - Native PostgreSQL support gives you a better performance when you use + PostgreSQL. -Shared roster +Shared Roster groups - - Shared roster support have been improved: You can specify all users in a - virtual host for addition in a group. + - Shared Roster groups support has been enhanced. New is the ability to add + all registered users to everyone's roster. Detailed information about this + new feature can be found on http://ejabberd.jabber.ru/shared-roster-all -Web interface +Web Interface - - The Web interface internal code has been modified for better integration - and compliance with J-EAI. - - The Web interface is now compliant to XHTML 1.0 Transitional. - - Several bugs have been fixed. + - The web interface internal code has been modified for better integration + and compliancy with J-EAI, an ejabberd-based Enterprise Application + Integration platform. + - More XHTML 1.0 Transitional compliancy work was done. Transports - - A transport workaround can be enabled with the compile time option. You + - A transport workaround can be enabled during compilation. To do this, you can pass the "--enable-roster-gateway-workaround" option to the configure - script. For example: - ./configure --enable-roster-gateway-workaround - This option allows to add items with subscription "to" in roster by - sending <presence type='subscribed'/> stanza to user. This option is - needed for JIT ICQ transport. - Warning: By using this option, ejabberd is not fully XMPP compliant. + script. (./configure --enable-roster-gateway-workaround) + This option allows transports to add items with subscription "to" in the + roster by sending <presence type='subscribed'/> stanza to user. This option + is only needed for JIT ICQ transport. + Warning: by enabling this option, ejabberd will not be fully XMPP compliant + anymore. -Documentation and translations +Documentation and Internationalization - - Documentation has been improved to cover more topics. - - Translations have been updated to support the new features. + - Documentation has been extended to cover more topics. + - Translations have been updated. Bugfixes - This release contains several bugfixes. - - Among other bugfixes include improvements to the Client-to-Server - connection management module. Please refer to the ChangeLog file supplied + - Among other bugfixes include improvements to the client-to-server (c2s) + connection management module. + - Please refer to the ChangeLog file supplied with this release regarding all improvements in ejabberd. -Erlang version supported - - You now need at least Erlang/OTP R9C to be able to run ejabberd 1.0.0. + Installation Notes + + +Supported Erlang Version -Installers + - You need at least Erlang/OTP R9C to run ejabberd 1.0.0. - Installers are provided for Microsoft Windows and Linux/x86. The Linux - installer includes Erlang ASN.1 modules for LDAP authentication support. - Installers are available from: +Installation + + Installers are provided for Microsoft Windows and Linux/x86. + Installers can be retrieved from: http://www.process-one.net/en/projects/ejabberd/download.html -Migration +Migration Notes - Before any migration, ejabberd system and database must be properly - backed-up. - - System migrating from a previous ODBC based install will need to change - their relational database schema. The following SQL commands must be run - on the database: - CREATE SEQUENCE spool_seq_seq; - ALTER TABLE spool ADD COLUMN seq integer; - ALTER TABLE spool ALTER COLUMN seq SET DEFAULT nextval('spool_seq_seq'); - UPDATE spool SET seq = DEFAULT; - ALTER TABLE spool ALTER COLUMN seq SET NOT NULL; + backed up. + - When upgrading an ODBC-based installation, you will need to change the + relational database schema. The following SQL commands must be run on the + database: + CREATE SEQUENCE spool_seq_seq; + ALTER TABLE spool ADD COLUMN seq integer; + ALTER TABLE spool ALTER COLUMN seq SET DEFAULT nextval('spool_seq_seq'); + UPDATE spool SET seq = DEFAULT; + ALTER TABLE spool ALTER COLUMN seq SET NOT NULL; References - The ejabberd feature sheet helps comparing with other Jabber/XMPP - servers: - http://www.process-one.net/en/projects/ejabberd/docs/features.pdf - Contributed tutorials of interest are: - Migration from Jabberd1.4 to ejabberd: http://ejabberd.jabber.ru/jabberd1-to-ejabberd |