Skip to content

Commit

Permalink
this might be it?
Browse files Browse the repository at this point in the history
  • Loading branch information
mikeferguson committed Dec 10, 2024
1 parent f4986bb commit 46a3d08
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion documentation/contributing/releases/index.markdown
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ title: Releases

# Release Process

While the latest code is always available in source format, we also make releases available in binary formats. Releases are made on a periodic basis into all of the currently supported <a href="distribution">ROS distributions</a>. The decision to make a new release is usually made during the monthly maintainer meeting.
While the latest code is always available in source format, we also make releases available in binary formats. Releases are made on a periodic basis into all of the currently supported <a href="/about/distribution">ROS distributions</a>. The decision to make a new release is usually made during the monthly maintainer meeting.

New features and API or ABI breaking changes can be merged at any time into the `main` branch. For this reason, most ROS releases will have a stable branch named after the ROS release, for instance `jazzy`. These release-specific branches aim to maintain API and ABI compatibility for the life of the ROS distribution.

Expand Down

0 comments on commit 46a3d08

Please sign in to comment.