Skip navigation
All Places > Ignite Realtime Blog > 2010 > August
2010

Good things come to those who wait!

 

The Ignite Realtime Community is pleased to announce the beta for the next release of Openfire. This release contains a number of important  fixes and improvements to stability and XMPP protocol compliance. You can find a full list of fixed issues here. This beta is also the first version of Openfire to be released by the Ignite Realtime community under the Apache License v2.0.

 

You can download the 3.7.0 beta release here. Please provide us your feedback on the Ignite Realtime support forums. It would be helpful if you would tag your comments, discussions and questions with a tag that reads "openfire370beta"

 

As always, but particularly since this is a beta release, make sure to backup any existing version of Openfire and the persistent storage that it uses, before upgrading!

 

Some important security related notes to this release:

  • Openfire no longer ignores the system property to disallow password changes via XMPP. With previous releases, it was not possible to prevent users from changing their password via their XMPP connection. (CVE-2009-1596)
  • Fixed a XSS attack on the admin console login form.

 

Protocol compliance improvements:

  • Publish Subscribe (PubSub)
  • BOSH (http-bind) xml namespace compliance fix.

 

Some highlights of this beta release:

  • Improves how Openfire handles "idle" connections. Some of you may have  the system property xmpp.client.idle set to -1 to work around  previously broken behaviour. You may now let it default to 6 minutes or  set it to your preference.
  • Improved Openfire's caching to be less prone to memory exhaustion by correctly calculating cache size usage.
  • Fixed a bug where admin console login into a newly installed Openfire server would fail until restarted.
  • Fixed a bug with shared rosters within a LDAP environment.
  • Openfire now ships with the latest JRE (1.6.0u21).
  • A memory leak with the Personal Eventing Protocol (PEP) was fixed.
  • Openfire's custom log interface has been replaced with SLF4J and a Log4J backend.
  • Fix issues with self signed SSL certificates.
  • A number of improvements and fixes were made to the Multi-User Chat (MUC) configuration pages on the admin console
  • There were also some improvements made to the plugins.
  • There are also French, Russian, and Lithuanian langauge translation fixes for Openfire and some of the plugins.

You probably have noticed many recent changes with Ignite Realtime! Thanks to the help of Benjamin Sherman of Jive Software, the entire suite of Ignite Realtime servers and infrastructure have been migrated to a Contegix hosted location external to Jive. This was done so that the community could take administrative control of Ignite Realtime and push projects forward as we wanted without relying on help from Jive Software.

http://www.igniterealtime.org/images/ignite_logo.gif

So has Jive Software abandoned Ignite Realtime? No! They continue to generously fund the infrastructure and colocation costs at Contegix.  They also will participate with the community when appropriate. The community is now in tasked with moving projects forward!

 

So how will this work? At the moment, there is a handful of active community members that have been working hard to get the infrastructure setup. This infrastructure includes:

 

logo_atlassian1.png
jive-darkgloss-2600x1300.jpg

 

So who is running the show here? We currently do not have any formal community leadership process in place. The handful of us that are currently getting the infrastructure setup have been working together to make decisions to move Ignite Realtime forward.  With more community involvement and interest, we'll certainly wish to formalize roles and responsibilities soon.

 

So when will project X on Ignite make a new release? Depends Here is a brief summary of the various projects status:

  • Openfire is very close to a 3.7.0 beta release. Guus der Kinderen and others have been working hard to squash remaining bugs and get a formal beta release out the door.
  • Spark continues to struggle along and sure could use some developers to help get a formal release out the door. Please let us know if you are interested in helping out.
  • XIFF released version 3.0.0 just this week thanks to the work of Mark Walters. Congratulations on the new release!
  • Smack has seen recent development and could use more developers to help progress things along.
  • Tinder is developed by Guus and he continues to make improvements to the library projects like Openfire uses.
  • Spark Web has not seen development on Ignite for quite some time. Community member Dele Olajide has made a number of improvements to spark web on the version he maintains offsite.
  • Whack could use some development help, so please let us know if you are interested.

 

At the end of the day, the productivity of the Ignite Realtime Community depends on you! We have been given the power to push projects forward as fast as we wish, so let us take advantage of this wonderful infrastructure setup provided by Jive Software.

 

Onward and upward!

 

We are pleased to announce the release of XIFF 3.0.0!

This major release includes many bug fixes, improvements, and features over the previous beta release, including Digest-MD5 support and removal of all Flex dependencies for pure AS3 project support. This release also includes a new class namespace (igniterealtime instead of jivesoftware).

You can view the full change log here.

 

Download XIFF from here.

 

Nightly builds are also maintained for XIFF now. You can access those here.

 

Enjoy!

We  have just released Tinder  1.2.2, which is a maintenance release. It  fixes a number of bugs, features improved performance and has a number  of new features.

 

Download Tinder from: http://www.igniterealtime.org/downloads/index.jsp

Filter Blog

By date: By tag: