I think that we should document what our goals are with respect to binary/source compatibility as we reach 1.0.
I'd be inclined to propose the following:
1.0.2
is binary compatible with 1.0.0
and 1.0.1
.1.1.0
is not necessarily binary compatible with 1.0.0
.cats-kernel
module will remain binary-compatible across minor versions. Binary-incompatible changes to this module should only occur alongside a major version bump (which will be few and far-between).What do people think about the ones I have? Are there others that we should add?
One thing that I don't really know how to quantify is source-compatibility. In general I want us to strive for source-compatible changes, but as long as they aren't too intrusive, I think it's less of a concern than binary compatibility.
cc @johnynek and @mpilquist who I think are both interested in compatibility.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4