Hi Folks,

We are pleased to announce the final release of OpenMAMA 2.4.0 is now available:

https://github.com/OpenMAMA/OpenMAMA/releases/tag/OpenMAMA-2.4.0-release

As many of you will be aware, we have been working on this OpenMAMA release for months now and it is one of the biggest we have ever assembled - both in terms of features assembled and sheer quantity of new and modified lines of code.

At a high level, the main new functionality is in the following areas:

• Qpid proton broker support
• It is now possible to use the qpid payload on non-qpid transports and vice versa
• Support for Microsoft Visual Studio 2015
• CentOS / RHEL 7 support
• Fedora 23 support
  
• A default payload type may now be enabled via configuration
• Several changes made to work with recent OSX
• Publisher Events now in place to allow asyncronous publish time failures to be handled
  
• Dynamic entitlements now defines an entitlement interface which doesn't depend on OEA
  
• Dynamic Bridge loading now allows middleware and payload bridges to work without needing to register an enum with OpenMAMA
  

NB
for bridge developers, see updated wiki page detailing the changes required in the bridge which have changed slightly since our last notification: https://github.com/OpenMAMA/OpenMAMA/wiki/Dynamic-Bridge-Loading. If you have not made these changes since the first release candidate was cut in February, we recommend you do so ASAP to remain current with the project.

As well as new functionality, we have also been undergoing several major operational changes since the last OpenMAMA Release:

• Migrated Wiki, Issue tracking and code review all in Github out in the open (see http://github.com/OpenMAMA/OpenMAMA)
• Continuous integration now includes Microsoft Windows builds (see http://ci.openmama.org)
• All compiler warnings have been removed from our CentOS 6.x builds
• All supported unit tests should now pass on Avis

Another focal point of this release is a general bug scrub of all outstanding issues, leading to over 100 issues of various sizes being resolved since we moved to Github less than 6 months ago.

A special thanks to all developers, contributors and testers who helped is getting this out door.

Cheers,
Frank