Add deprecation section to webrtc style guide
No-Presubmit: True No-Try: True Bug: webrtc:12484 Change-Id: I800926c8e8c79344fc8034d3fbd452d11d7b301a Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/208405 Commit-Queue: Danil Chapovalov <danilchap@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Cr-Commit-Position: refs/heads/master@{#33315}
This commit is contained in:
committed by
Commit Bot
parent
e904161cec
commit
7013b3b5a4
@ -157,7 +157,7 @@ API_CHANGE_MSG = """
|
||||
You seem to be changing native API header files. Please make sure that you:
|
||||
1. Make compatible changes that don't break existing clients. Usually
|
||||
this is done by keeping the existing method signatures unchanged.
|
||||
2. Mark the old stuff as deprecated (see RTC_DEPRECATED macro).
|
||||
2. Mark the old stuff as deprecated (use the ABSL_DEPRECATED macro).
|
||||
3. Create a timeline and plan for when the deprecated stuff will be
|
||||
removed. (The amount of time we give users to change their code
|
||||
should be informed by how much work it is for them. If they just
|
||||
|
||||
Reference in New Issue
Block a user