Due to the importance of getting API right, there is a required review process for changes to the Traffic Server API. For every API change, the developer should post a message to the dev@ list that
- references the relevant jira ticketGithub Issue or PR
- explains the motivating problem and rationale
- shows the actual API change itself (ie. API signatures, etc)
- documents the semantics of the proposed API
- notes any ABI or compatibility implicates
...