gz-msgs
gz-msgs copied to clipboard
Document policy for message modification
We can't modify messages within a major release because that would break ABI for the generated C++ classes.
How about in between releases? How do we tick-tock the change / removal of message fields?
We should decide on a policy and document it.