Summing up the versioning discussion

[Cantor, Scott]

 > I'm not getting it, apologies. Regarding third party dependencies, I
> thought the "policy" was :
> 
> patch : update for bug fixes
> minor : update or add
> major : update or add or remove

I was being more general with the "no", but yes, it included the possibility of updates for bug fixes, but the policy so far has been that we only do it when we have to to fix a problem. Not just to stay current.

I should have said "we don't update third party libraries as a routine step" for patch releases.

To be honest, I don't like the policy, and it isn't the one I follow with the SP. But it runs together with the API problem because when you update dependencies, you can easily end up changing your API if you inherit from any classes in them, so it sort of goes hand in hand. But when you allow for exceptions to fix bugs in a patch, then it seems to me you've just created a possible exception to the API change rule too.

-- Scott