Skip to content

Declare our public API #248

@chapulina

Description

@chapulina

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions