Status of 5.0 dev?

Submitted by Anonymous on Mon, 2010-02-08 23:46

Hey guys...

Just wondering how 5.0 is going.

I'm starting a new project that will require extensive customization (authentication, stats, and MUC extensions) - and I'm wondering whether I should start with the stable branch, or if 5.0 is compelling enough (and stable/coming-soon-enough!) for me to work with now, straight out of SVN?

If I do work with the 4.x branch, will it be hellish to 'port' my modules and plugins to 5.x?

Thanks for your input!

-Lorenzo

Artur Hefczyc's picture

Probably I forgot to update

Probably I forgot to update the README file, sorry for this.
You can have a look at all tagged code for the released version: https://svn.tigase.org/reps/tigase-server/tags/
and there is also a development branch available for version: 5.1.0:
https://svn.tigase.org/reps/tigase-server/branches/tigase-server-5.1.0/

sorry. never mind. my

sorry. never mind. my mistake. the version shown is 5.x

The svn

The svn (https://svn.tigase.org/reps/tigase-server/trunk/ server) is showing version 4.3.1-b1858 in README. Where can I get the 5.0?

Artur Hefczyc's picture

Good question, which is

Good question, which is answered here.

whats new in tigase5.0 api ?

whats new in tigase5.0 api ?

Thanks Artur, that's just the

Thanks Artur, that's just the sort of feedback I needed. I guess the MUC module is already compatible with the 5.x server code?

-Lorenzo

Artur Hefczyc's picture

The current SVN trunk is

The current SVN trunk is fairly stable, it passed most of my automatic tests and I am preparing to release a new version this week.

If I find some bugs which have to be fixed before final version, however, I will publish 5.0.0 beta anyway because I know that quite a few people wait for it to make use of the new API available.

If you start a new project then I would highly recommend to start with 5.x right now. There is no revolution, rather evolution so porting to a new version is not too hard but there are a few new additions to the API which really help. Besides it is always better to avoid porting if you can use the new API straight away.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.