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
Specifically we will aim to have two types of releases
Source release: Suitable branches and rmf.repos files with exact tags of each package will be created here. Similar to 21.09
humble-release
iron-release
Note: Instead of repos files consider relying on rosinstall_generator.
Debian (Binary) release (distributed via ROS Buildfarm):
humble
iron
rolling
Note: The debian release will not include packages from rmf_demos given the known issues [#todo: add link] with distributing these packages.
As part of this release, we will aligned with conventions and practices of ROS 2 releases. One exception will be the default branch for development will continue to be main in Open-RMF as opposed to rolling. We will bloom into ROS 2 Rolling from main.
TODO Checklist (to be completed in order)
Sync main branches with rolling so that we can deprecate rolling. Update: We can't delete rolling since for some repos we can't bring over commits with tags from rolling into main due to linear history constraints.
Convert all pkg's CHANGELOGS.md files to CHANGELOG.rst. This is to align with REP 132 and will greatly improve the ease of updating changelogs in the future as they will be auto-populated when running catkin_generate_changelog.
Bump minor version on main for all repos before creating iron branch. This will keep iron pkgs always ahead of humble and we can release API breaking features into iron.
The release will target:
Specifically we will aim to have two types of releases
rmf.repos
files with exact tags of each package will be created here. Similar to 21.09humble-release
iron-release
humble
iron
rolling
As part of this release, we will aligned with conventions and practices of ROS 2 releases. One exception will be the default branch for development will continue to be
main
inOpen-RMF
as opposed torolling
. We will bloom into ROS 2 Rolling frommain
.TODO Checklist (to be completed in order)
main
branches withrolling
so that we can deprecaterolling
. Update: We can't delete rolling since for some repos we can't bring over commits with tags from rolling into main due to linear history constraints.CHANGELOGS.md
files toCHANGELOG.rst
. This is to align with REP 132 and will greatly improve the ease of updating changelogs in the future as they will be auto-populated when running catkin_generate_changelog.main
for all repos before creatingiron
branch. This will keepiron
pkgs always ahead ofhumble
and we can release API breaking features intoiron
.iron
branch frommain
on all repos.humble
torolling
humble
to matchrolling
-> mergedrolling
intohumble
and did a patch bump.humble
tomain
forrmf_utils
humble
tomain
for rmf_visualization_msgsiron
humble
main
for all repos so thatmain
remains ahead ofiron
.rolling
iron
branchiron-release
with exact tags of release pkgsiron-release
with date of update egrelease-iron-230526
humble
branchhumble-release
with exact tags of release pkgs: https://github.com/open-rmf/rmf/blob/humble-release/rmf.reposhumble-release
with date of update egrelease-humble-230526
rmf_dev
metapackageThe text was updated successfully, but these errors were encountered: