I thought I’'d provide some info on the current project roadmap. All of this is in the issue tracker, but I thought a forum post might be helpful too.
We’‘ve continued to go pretty crazy on internal refactoring during the last couple of weeks. That means that another release in the 2.0.x series isn’‘t very practical. So, we’‘ll be pushing out a 2.1.0 release much sooner than planned. At this point, I’'d estimate that the release is about two weeks away.
Some highlights on what will be in 2.1.0 –
Plugin support (JM-60). Plugins extend the server and can dymanically modify content in the admin console. They will provide a very easy way for new developers to get involved in the project. We plan on having a plugin registry up on the site before long, which will also be nice. All the core plugin work is already complete, and a plugin developer guide is in progress. You can find that document in CVS or in new nightly builds.
The core packet model in Jive Messenger is being completely refactored (JM-61). This won’'t affect end-users directly all that much, but fixes a lot of issues and makes further development much easier.
LDAP is slated to be fixed (JM-10).
We’'re going to try to get in a few features that users have been requesting, such as JM-22 (shared groups in rosters), JM-21 (broadcast service), and JM-63 (tray icon support for the launcher).
Since the 2.1.0 release is coming sooner than expected, a number of features won’'t be in this release. This includes server to server, and SASL.