You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should formally declare what's part of our public API, so that users are aware of what will be kept stable and what's subject to change without warning or tick-tock.
Take into account:
Public headers and what it means if they're in a details folder
CMake functions from gz-cmake
CLI arguments
Binary symbols
Protobuf namespaces
A good reference is REP-2004 and the quality declarations of existing packages, like rclcpp.
We could place this documentation in releases together with versioning and deprecation strategies.
The text was updated successfully, but these errors were encountered:
We should formally declare what's part of our public API, so that users are aware of what will be kept stable and what's subject to change without warning or tick-tock.
Take into account:
details
foldergz-cmake
A good reference is REP-2004 and the quality declarations of existing packages, like rclcpp.
We could place this documentation in releases together with versioning and deprecation strategies.
The text was updated successfully, but these errors were encountered: