Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[ros2-humble] writing down the backport tool and its usage (#377) #378

Merged
merged 1 commit into from
Jun 27, 2024
Merged

[ros2-humble] writing down the backport tool and its usage (#377) #378

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 16 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,22 @@ Diagnostics messages that are not aggregated can be visualized by [`rqt_runtime_
- **Iron Irwini** by the [`ros2-iron` branch](https://github.com/ros/diagnostics/tree/ros2-iron)
- **Jazzy Jalisco** by the [`ros2-jazzy` branch](https://github.com/ros/diagnostics/tree/ros2-jazzy)

## Workflow

New features are to be developed in custom branches and then merged into the `ros2` branch.

From there, the changes are backported to the other branches.

## Backport Tooling

This tool has proven to be useful: [backport](https://www.npmjs.com/package/backport)

Use this command to port a given PR of `PR_NUMBER` to the other branches:

```bash
backport --pr PR_NUMBER -b ros2-humble ros2-iron ros2-jazzy
```

# Versioning and Releases

- (__X__.0.0) We use the major version number to indicate a breaking change.
Expand Down
Loading