Date   
OpenMAMA 2.3.0 Released

Damian Maguire <DMaguire@...>
 

Evening all, 

It's been a long time coming, but we're happy to announce the release of OpenMAMA 2.3.0. Included in the new release are a wide range of new and improved features, including:
  • Qpid Proton middleware and payload bridge, running on both Linux and Windows, and with full market data support.
  • Completely new SCons based build infrastructure.
  • New and improved market data capture and replay tools, including sample level 1 and level 2 market data, symbol lists and data dictionary.
  • Redhat and Centos Linux releases are now packaged as RPMs.
  • Over 1500 unit tests.
  • Wide ranging bug fixes and other code improvements. 
The new release is available for download as binary releases, RPMs or a source tarball from the main OpenMAMA releases site, while the sample data, dictionary and symbol lists are available from the downloads page. We've also pulled together a blog post providing a bit more detail regarding the changes within the release, which is available here.

The latest release has seen a significant amount of work, with a large contribution coming from the community, and we're grateful for all the support we've received when working on it. However, as with all software there may still be some bugs, so if you have some trouble getting started, or spot any issues please raise them on the mailing lists or on our Bugzilla.

Looking forward to hearing your feedback.

Thanks,

Damian

Damian Maguire – Senior R&D and OpenMAMA Specialist
IntercontinentalExchange | NYSE Technologies
24-26 Adelaide Exchange | Belfast, BT2 8GD
Tel: +44 2890 822 282 (ext: 452161) | Mob: +44 7540 204 077

This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange Group, Inc. (ICE), NYSE Euronext or any of their subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.

OpenMAMA 2.3.1 Released

Damian Maguire <DMaguire@...>
 

Morning all, 

It's with great pleasure that we're announcing the latest point release OpenMAMA, 2.3.1, is now available. This release has seen a large number of changes, with a particular focus on improving the overall build process across platforms. As such, there's been a lot of work on Scons and the Visual Studio solution files. Equally, with a lot of community engagement, we've continued to address bug fixes, keep MAMDA up to date, improve performance and code hygiene, enhance both the Avis and Qpid bridges, and see a large chunk of new open source functionality in the form of the Field Cache. 

A bit more detail can be found in the announcement blog post on the OpenMAMA website, here.

The source code for this release can be found in the OpenMAMA git repository, where 2.3.1 is now the head of the master branch. The following source, RPM and binary releases are also available:


Looking forward, there's a lot of exciting changes coming around the corner – the dynamic loading working group is in full swing, and we're expecting some of the work performed there to start filtering into the main repository with the coming months, which will not only provide new features, but also help future proof OpenMAMA as we go forward. Similarly, we've seen a great uptick in engagement from the whole community, in terms of not only code contributions, but also testing, bug reporting and general feedback. This looks set to continue to grow,  so expect to see a lot of interesting work coming over the next few months. At present we're expecting a new release around the end of September, so keep your eye out for that.

Thanks again for all the assistance from everyone who contributed, and as always if anyone has any questions feel free to drop me a mail.

Damian

Damian Maguire – Senior R&D and OpenMAMA Specialist
IntercontinentalExchange | NYSE Technologies
24-26 Adelaide Exchange | Belfast, BT2 8GD
Tel: +44 2890 822 282 (ext: 452161) | Mob: +44 7540 204 077

This message may contain confidential information and is intended for specific recipients unless explicitly noted otherwise. If you have reason to believe you are not an intended recipient of this message, please delete it and notify the sender. This message may not represent the opinion of IntercontinentalExchange Group, Inc. (ICE), NYSE Euronext or any of their subsidiaries or affiliates, and does not constitute a contract or guarantee. Unencrypted electronic mail is not secure and the recipient of this message is expected to provide safeguards from viruses and pursue alternate means of communication where privacy or a binding message is desired.

OpenMAMA 2.4.0 Released

Frank Quinn <fquinn.ni@...>
 

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

OpenMAMA 6.1.0 En Route

Frank Quinn <fquinn.ni@...>
 

Hi Folks,

In the interest of simplifying version compatibility, OpenMAMA's next release version is going to be 6.1.0. I appreciate it's a big jump but it should make the following things clear to the community and anyone watching the project:
  1. OpenMAMA is the equivalent to Vela's "MAMA 6" (Vela have also agreed to move to 6.1.x to align with OpenMAMA).
  2. Users of both Vela's Enterprise release of MAMA and OpenMAMA can easily see what equivalent versions will be.
  3. Users upgrading from MAMA 5 can have more sane #ifdefs in their code if they're trying to support both versions during migration.
I plan on taking the cut within the next week, so if anyone has any issues that they would like to be included or patches you would like to be included in the next release, please reply to this thread with details.

Cheers,
Frank

Re: [Openmama-dev] OpenMAMA 6.1.0 En Route

Dmitri Fedorov
 

Hi Frank,

This is a cut from the "next" branch, right? The one that was going to be 2.4.2 and planned for the end of summer?

Regards,
Dmitri Fedorov
Software Architect
Solace Systems, Inc.
Ottawa, ON Canada

Solace Systems accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Solace Systems.

On 29 July 2016 at 14:54, Frank Quinn <fquinn.ni@...> wrote:
Hi Folks,

In the interest of simplifying version compatibility, OpenMAMA's next release version is going to be 6.1.0. I appreciate it's a big jump but it should make the following things clear to the community and anyone watching the project:
  1. OpenMAMA is the equivalent to Vela's "MAMA 6" (Vela have also agreed to move to 6.1.x to align with OpenMAMA).
  2. Users of both Vela's Enterprise release of MAMA and OpenMAMA can easily see what equivalent versions will be.
  3. Users upgrading from MAMA 5 can have more sane #ifdefs in their code if they're trying to support both versions during migration.
I plan on taking the cut within the next week, so if anyone has any issues that they would like to be included or patches you would like to be included in the next release, please reply to this thread with details.

Cheers,
Frank

_______________________________________________
Openmama-dev mailing list
Openmama-dev@...
https://lists.openmama.org/mailman/listinfo/openmama-dev


Re: [Openmama-dev] OpenMAMA 6.1.0 En Route

Frank Quinn <fquinn.ni@...>
 

Hi Dmitri,

Yes this is the release that we were going to call 2.4.2 and ideally release at the end of next month.

Cheers,
Frank


On Fri, 29 Jul 2016, 20:19 Dmitri Fedorov, <dfedorov.solace@...> wrote:
Hi Frank,

This is a cut from the "next" branch, right? The one that was going to be 2.4.2 and planned for the end of summer?

Regards,
Dmitri Fedorov
Software Architect
Solace Systems, Inc.
Ottawa, ON Canada

Solace Systems accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Solace Systems.

On 29 July 2016 at 14:54, Frank Quinn <fquinn.ni@...> wrote:
Hi Folks,

In the interest of simplifying version compatibility, OpenMAMA's next release version is going to be 6.1.0. I appreciate it's a big jump but it should make the following things clear to the community and anyone watching the project:
  1. OpenMAMA is the equivalent to Vela's "MAMA 6" (Vela have also agreed to move to 6.1.x to align with OpenMAMA).
  2. Users of both Vela's Enterprise release of MAMA and OpenMAMA can easily see what equivalent versions will be.
  3. Users upgrading from MAMA 5 can have more sane #ifdefs in their code if they're trying to support both versions during migration.
I plan on taking the cut within the next week, so if anyone has any issues that they would like to be included or patches you would like to be included in the next release, please reply to this thread with details.

Cheers,
Frank

_______________________________________________
Openmama-dev mailing list
Openmama-dev@...
https://lists.openmama.org/mailman/listinfo/openmama-dev

OpenMAMA 6.1.0 Released

Frank Quinn <fquinn.ni@...>
 

Hi Folks,

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

https://github.com/OpenMAMA/OpenMAMA/releases/tag/OpenMAMA-6.1.0

This mostly a maintenance / bugfix release, but it also jumps the version number from 2.4.1 to 6.1.0. I appreciate it's a big jump but it should make the following things clear to the community and anyone watching the project:

  • OpenMAMA is the equivalent to Vela's "MAMA 6" (Vela have also agreed to move to 6.1.x to align with OpenMAMA).
  • Users of both Vela's Enterprise release of MAMA and OpenMAMA can easily see what equivalent versions will be.
  • Users upgrading from Vela's older MAMA 5 can have more sane #ifdefs in their code if they're trying to support both versions during migration.
Note that bridge has not been changed as part of this release so all bridges and plugins which worked with 2.4.x will also work with 6.1.x.

At a high level, the main new functionality is in the following areas:
  • Removed all known valgrind reported memory leaks from our CI test bed and API
  • Avis now removed (see the mailing list entry)
  • Added Payload and Middleware unit tests on Visual Studio projects
  • Added ability to provide a separate timeout for recaps
  • Fixed issue where book recaps were being ignored duing FT takeover
  • Fixed issue where wildcard subscription OnMsg callback is called with NULL instead of topic
  • Wired up mamamsg vector price and vector datetime field types
  • Qpid support to stop publishing to departed subscribers added
  • Fixed core on startup where no entitlements were defined
  • Fixed race condition deadlock in mamaDispatcher_destroy

For a complete list of all 69 issues and pull requests included in this release, please see here: https://github.com/OpenMAMA/OpenMAMA/milestone/5?closed=1

As well as new functionality, we have also continued with a few devops changes since the last OpenMAMA Release:
  • New python script in place to do jenkins CI builds
  • Qpid proton build script now modified to include the qpid proton DLL on windows scons builds
  • Modified release generating script to allow binary drops for RC releases
  • Added Fedora 24 RPM and removed Fedora 21 RPM
  • Github landing page has gotten a bit of a facelift including CI status
A special thanks to all developers, contributors and testers who helped is getting this out door.

Cheers,
Frank

OpenMAMA 6.2.0 Released

Frank Quinn <fquinn.ni@...>
 

Hi Folks,

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

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

This release bumps the version of OpenMAMA up to 6.2.0 due to recent MAMA Payload changes which could potentially break the bridge for payload bridges which treat mamaDateTime as a U64 pointer and attempt direct access. See the RFC on the change for for more details (particularly payload bridge developers as changes may be required).

Key changes and bugfixes included in this release:

  • New extended MamaDateTime changes to support date ranges beyond the 2038 problem
  • Added thread pinning for process thread affinity
  • Performance improvements made for mamaDqPublisher_send
  • Fixed transient access violation issues in windows when using wtimegm
  • New MAMA methods for looking up middleware and payload bridges
  • Performance improvements to mamaproducerc_v2
  • Added new document generating script for updating openmama.github.io
  • Added new helper method for finding a file in a delimited path (e.g. PATH or WOMBAT_PATH)
  • Added new helper method for loading in a MAMA format symbol file in a standard way

For a complete list of all 24 issues and pull requests included in this release, please see here: https://github.com/OpenMAMA/OpenMAMA/milestone/6?closed=1

As well as new functionality, we have also continued with a few devops changes since the last OpenMAMA Release:

  • Main github landing page now includes Travis CI buttons
  • Nightly RPM builds are now available and accessible via the github landing page
  • The ci-run python script is now used across all platforms simplifying the CI process

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

Cheers,
Frank

Re: OpenMAMA 6.2.0 Released

Frank Quinn <fquinn.ni@...>
 

Apologies folks, for some reason this email seems to render badly in outlook.

If this effects you, check out the official announcement instead: http://www.openmama.org/news/openmama-620-released


On Thu, Mar 30, 2017 at 2:30 PM, Frank Quinn <fquinn.ni@...> wrote:

Hi Folks,

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

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

This release bumps the version of OpenMAMA up to 6.2.0 due to recent MAMA Payload changes which could potentially break the bridge for payload bridges which treat mamaDateTime as a U64 pointer and attempt direct access. See the RFC on the change for for more details (particularly payload bridge developers as changes may be required).

Key changes and bugfixes included in this release:

  • New extended MamaDateTime changes to support date ranges beyond the 2038 problem
  • Added thread pinning for process thread affinity
  • Performance improvements made for mamaDqPublisher_send
  • Fixed transient access violation issues in windows when using wtimegm
  • New MAMA methods for looking up middleware and payload bridges
  • Performance improvements to mamaproducerc_v2
  • Added new document generating script for updating openmama.github.io
  • Added new helper method for finding a file in a delimited path (e.g. PATH or WOMBAT_PATH)
  • Added new helper method for loading in a MAMA format symbol file in a standard way

For a complete list of all 24 issues and pull requests included in this release, please see here: https://github.com/OpenMAMA/OpenMAMA/milestone/6?closed=1

As well as new functionality, we have also continued with a few devops changes since the last OpenMAMA Release:

  • Main github landing page now includes Travis CI buttons
  • Nightly RPM builds are now available and accessible via the github landing page
  • The ci-run python script is now used across all platforms simplifying the CI process

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

Cheers,
Frank