Skip to content

Conversation

@cullenstoneAS
Copy link
Collaborator

3.1.1 release

dvangeyn-as
dvangeyn-as previously approved these changes Jun 29, 2023
@icolwell-as
Copy link
Member

Hey @cullenstoneAS , for ros packages/repos that have both a ROS1 and ROS2 version of the exact same package name, we have been using versions 200X.X.X for the ROS2 version. For example if the ROS1 version is currently 3.1.0, then the ROS2 version with the same features should be 2003.1.0.
It's just a way to quickly/easily tell if we are working with a ROS1 or ROS2 package based on the version tag, and a way to release both ROS1 and ROS2 versions from the same git repo without things getting too messy.

@cullenstoneAS cullenstoneAS merged commit 41c0d60 into ros2_master Jul 11, 2023
@cullenstoneAS cullenstoneAS deleted the 3.1.1_release branch July 11, 2023 13:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants