Re: OpenMAMA-2.4.0-rc1 Now Available
Alpert, Reed <reed.alpert@...>
Submitted one pull request for Sconscript.win to create entitlementlibraries.c.
With that the build works fine via scons on Windows 7 32b/64b, RHEL5 32b/64b, RHEL6 32b/64b.
Reed Alpert | Corporate & Investment Bank | Market Data Services | J.P. Morgan | 4 Metrotech Center, 23rd Floor, Brooklyn, NY 11245 | T: 718.242.5198 | M: 917.414.4613 | reed.alpert@...
Alternate Contact: CIB Market Data Services Engineers | CIB_Market_Data_Services_Engineers@...
From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Frank Quinn
Sent: Thursday, February 18, 2016 6:37 AM
Subject: [Openmama-dev] OpenMAMA-2.4.0-rc1 Now Available
We are pleased to announce the first release candidate for OpenMAMA 2.4.0 is now available:
As many of you will be aware, we have been working on closing off the work required for a new OpenMAMA release for several weeks 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.
With that in mind, I would appreciate everyone’s help in trying out the latest release candidate and helping weed out any bugs or unexpected behavior which may have crept in, or may be specific to your environment / bridges. At a high level, the main new functionality is in the following areas:
· Qpid proton broker support
· Several qpid proton bridge bug fixes including fixing support for using the qpid payload on non-qpid transports and vice versa
· CentOS / RHEL 7 support
· Timer fixes
· Several changes to work with recent OSX
· Publisher Events
· Dynamic Entitlements (phase 1 - mainly focused on defining existing interface points)
· Dynamic Bridge loading (the ability to load any middleware bridge, even if there is no reference to it in OpenMAMA code, and adding flexibility to the bride interface).
· Ability to specify a default payload via configuration
With that in mind, we recommend that any testing you plan on doing pays particular attention to those areas.
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
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.
This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates (collectively, "JPMC"). This transmission may contain information that is proprietary, privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMC for any loss or damage arising in any way from its use. Please note that any electronic communication that is conducted within or through JPMC's systems is subject to interception, monitoring, review, retention and external production in accordance with JPMC's policy and local laws, rules and regulations; may be stored or otherwise processed in countries other than the country in which you are located; and will be treated in accordance with JPMC policies and applicable laws and regulations. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities.