Do not use current trunk in production

XIFF
1

Please note that the commit http://fisheye.igniterealtime.org/changelog/xiff?cs=13123 and onwards for few iterations, are not meant to use in production.

The XML migration is a huge change in the library.

It will take a moment to get everything working as before.

I decided to commit unfinished work in order to get feedback sooner and to avoid anyone working on the same code.

My goal is to finish the http://issues.igniterealtime.org/browse/XIFF-32 by the time XIFF 3.1.0 will be released.
openfire.xml (3832 Bytes)
gss.conf.zip (362 Bytes)
jabber.keytab.zip (304 Bytes)
krb5.ini.zip (333 Bytes)

2

I think you should still be committing to a branch. We could promote that branch if you want, but making the trunk unusable for production doesn’t seem like the best route.

3

Yes and no.

I decided to go this way as there currently are no other developer who is actively working on the code.

Additionally I did want the maximum visibility of then changes, thus used trunk, instead of the old branch.

With this I just want to speed up finding all the bugs and get the migration done as soon as possible.