Open jrudolph opened 7 years ago
try to keep binary compatibility not keeping it would somewhat discourage building third-party extensions which would be hard to use if we don't keep our API binary compatible
How many such extensions libraries are there, how many do we expect? 10, 100, 1000?
Wouldn't it be reasonable that such libraries release a new version when we release a new major version as long as we don't do it too often? If binary incompatible changes are collected and done all at the same time (bumbing the major version) for example twice per year?
Initial thinking:
Directives
andXYZDirectives
) and discourage from extendingMultipart
change which is a binary-compatibility breaking change which was somewhat unlikely to be noticed@experimental
documentation or annotation marker that marks API that is not yet stable (#438)@experimental
API need to be promoted after a fixed period of time?@experimental
API?