Date   
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