On Thu, Dec 18, 2014 at 07:51:34PM +0100, Thomas M wrote:
Is it intended that such changes which are transparent to end-users do not become reflected in the change-logs? In my case I have the troubles that now firstly all my existent test cases are invalidated (the lesser issue) and that in general reproducibility among runs is not provided any more if I upgrade to 1.57 (the greater issue).
I can only second that! It took me a while to work out the cause of discrepancies in our case, and I've read the changelogs many times, following up any mention of "breaking change" into the code to see if it could have something to do with what we've observed. We have skipped a version and it was a lot of work to isolate and fix this issue as we initially thought it was down to other development work that already happened and that required the latest version of boost. If it was in the changelog we would have found it much sooner. On the positive side, our tests are now much more robust to that sort of changes. :) -- Семен Тригубенко http://trygub.com