Lines Matching refs:change
1 # How to change BoringSSL's API
5 Ultimately, the strategy for each breaking change is decided on a case-by-case basis. This document…
9 …change, etc. But this is a poor approximation of the true impact. Removing an API may not a breaki…
11 Thus, we do not think about whether a change is formally a breaking change, but about the *risk* of…
15 … commit message, prefixed by `Update-Note: `. This can include what this change may break and inst…
19 …in various Code Search instances. This can predict the impact of a risky change and identify code …
21 ## Evaluate a change's cost
23 If some change has high cost (from having to fix consumers) and relatively little benefit to Boring…
25 Conversely, a change that leads to a major improvement to all BoringSSL consumers, at the cost of f…
29 …change. While unexpected breakage is always possible, we generally consider it the responsibility …
39 …e: perhaps the same code cannot simultaneously work before and after the change, or perhaps there …
41 In that case, a multi-sided change may be more appropriate:
43 1. Upload the breaking change to Gerrit, but do not submit it yet. Increment the `BORINGSSL_API_VER…
44 …ON < N` preprocessor logic. Leave a comment to remove this later, linking to your BoringSSL change.
45 …` check has propagated to relevant copies of the consuming repository, submit the BoringSSL change.
46 4. When the BoringSSL change has propagated to relevant copies of BoringSSL, remove the staging log…
48 Finally, in some cases, the consumer's change may be committed atomically with the BoringSSL update…
58 If some parameter now must be `NULL`, change the type to an opaque struct pointer. Consumers passin…
66 …t, we may fix the consumer, make a small fix to BoringSSL, or revert the change to either try agai…
72 …change, prefer to make the breaking change first—before committing larger changes. Or, when …
78 … but only a small subset is actually used. So we can and occasionally do change these behaviors. T…
82 …nges to BoringSSL over patching third-party code, unless the third-party change fixes a security p…
86 If the patch to support a BoringSSL change can be generally useful to the third-party project, send…
88 …problematic to OpenSSL too. Consider filing a bug with them to suggest a change, either in new cod…