{{Quickfixn}} getting rid of deprecations in next release

[Grant Birchmeier]

Hi all again,

I plan on getting rid of deprecated code in the next release.

I don't think this will affect many people, because most of the
deprecations are deep in engine code that most clients don't touch.

However, if you see deprecation warnings when you are building your app, I
highly encourage you to get rid of those.  Most deprecation warnings should
tell you what the right thing to call is, so I think it would be an easy
task.  If you have any questions about any deprecation warnings, please ask
(because I probably wrote those warnings!).

Note: I will not be bumping the major release number, e.g. this will not be
"QuickFIX/n 2.0".  I know that, technically, semantic versioning would
require me to do that, but (1) I don't think this will actually affect
anyone, and (2) this isn't going to "feel" like a major release and I don't
want the new number to give anyone a false idea.

-Grant

-- 
Grant Birchmeier
Connamara Systems, LLC
http://connamara.com

-- 
This email, along with any attachments, is confidential. If you believe you 
received this message in error, please contact the sender immediately and 
delete all copies of the message. Thank you from Connamara Systems, LLC.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20221215/526a36ef/attachment.htm>