Chapril
/
xmpp.chapril.org-ejabberd
mirror of https://github.com/processone/ejabberd.git
24
1
Fork 0
Code Releases Activity

fixed typos: 

SVN Revision: 462
This commit is contained in:
Mickaël Rémond 2005-12-13 16:53:26 +00:00
parent 7e70badf23
commit 8bc7f768de
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/release_notes_1.0.0.txt
View File

@ -4,8 +4,8 @@
This document describes the main changes in ejabberd 1.0.0. This version is This document describes the main changes in ejabberd 1.0.0. This version is
compliant with the XMPP (eXtensible Messaging and Presence Protocol) compliant with the XMPP (eXtensible Messaging and Presence Protocol)
standard. ejabberd is the first Open Source server to fully comply to the standard. ejabberd is the first Open Source server claiming to fully
XMPP standard. comply to the XMPP standard.
The code can be downloaded from the Process-one website: The code can be downloaded from the Process-one website:
http://www.process-one.net/en/projects/ejabberd/ http://www.process-one.net/en/projects/ejabberd/
@ -55,8 +55,10 @@ Web interface
Transports Transports
- A transport workaround can be enabled with the compile time option: - A transport workaround can be enabled with the compile time option. You
--enable-roster-gateway-workaround 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 This option allows to add items with subscription "to" in roster by
sending <presence type='subscribed'/> stanza to user. This option is sending <presence type='subscribed'/> stanza to user. This option is
needed for JIT ICQ transport. needed for JIT ICQ transport.
@ -92,7 +94,6 @@ Migration
- System migrating from a previous ODBC based install will need to change - System migrating from a previous ODBC based install will need to change
their relational database schema. The following SQL commands must be run their relational database schema. The following SQL commands must be run
on the database: on the database:
;; To update from previous table definition:
CREATE SEQUENCE spool_seq_seq; CREATE SEQUENCE spool_seq_seq;
ALTER TABLE spool ADD COLUMN seq integer; ALTER TABLE spool ADD COLUMN seq integer;
ALTER TABLE spool ALTER COLUMN seq SET DEFAULT nextval('spool_seq_seq'); ALTER TABLE spool ALTER COLUMN seq SET DEFAULT nextval('spool_seq_seq');