Re: OpenMAMA 2.3.1 Point Release
Tick42 will download and build the RC when it is available and test it out with our RMDS bridge and QPID
From: openmama-dev-bounces@... [mailto:openmama-dev-bounces@...] On Behalf Of Damian Maguire
Sent: 13 June 2014 4:57 PM
Subject: [Openmama-dev] OpenMAMA 2.3.1 Point Release
Following some of the interest there has been in a few of the changes in next, and given the time since we did the 2.3.0 release, it seems like a good time for a point release. Therefore over the next few weeks we're going to start pulling together OpenMAMA 2.3.1. At this stage I'd like to firm up a few details, and request some community assistance.
Firstly, the process we will be following:
So, what I need now is volunteers to test the release candidate - all that's required is that you run through a few tests, and report any bugs or issues on our Bugzilla. If you're willing to spend an hour or two during the week of the 23rd June checking out and building OpenMAMA, and running a few tests, or sanity checking the RC RPM or Zip, can you let me know. In particular can you let me know what platform(s) you're going to be testing on, and if there are any specific features you're particularly interested in looking at (for example, the Visual Studio solution files, or MAMDA order book logic).
As always, if you have any questions let me know.
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.