Lines Matching +full:backwards +full:- +full:incompatible

1 # `rules_rust` backwards compatibility policy
3 This document defines the backwards compatibility policy for rules_rust and
10 A backwards compatible change has the property that a build that is green,
17 A backwards compatible release has the property that it only contains backward
22 backwards compatible changes.
27 Backwards incompatible changes will have to follow a process in order to be
34 All minor version number releases before version 1.0 can be backwards incompatible.
35 Backwards incompatible changes still have to follow the the process, but minimum
46 release had incompatible changes that broke `rules_rust`), it is acceptable to
63 Platforms subject to backwards compatibility policy are
64 `x86_64-unknown-linux-gnu` and `x86_64-apple-darwin` (platforms supported by `rules_rust`).
65 Process for moving a best effort platform to a supported platform is consensus-based.
69 `//rust:defs.bzl` is subject to the backwards compatibility policy. That means
72 `//rust/private/…` is not subject to the backwards compatibility policy. Content
75 `//cargo:defs.bzl` is subject to the backwards compatibility policy.
79 not subject to the backwards compatibility policy.
84 Incompatible build settings are subject to the backward compatibility policy,
85 meaning the behavior of the flag cannot change in a backwards incompatible way.
86 They should be added to `//rust:incompatible.bzl`.
90 bug fix is controversial. Incompatible changes to
94 ## How to make a backwards incompatible change?
100 3. Add a build setting into `//rust:incompatible.bzl` that removes the old
103 manually flip incompatible flags.