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)
[x] 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.
[x] 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.
[x] 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.
Yadunund
commented
1 year ago
The release will target:
Specifically we will aim to have two types of releases
Source release: Suitable branches and
rmf.reposfiles with exact tags of each package will be created here. Similar to 21.09humble-releaseiron-releaseDebian (Binary) release (distributed via ROS Buildfarm):
humbleironrollingAs 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
maininOpen-RMFas opposed torolling. We will bloom into ROS 2 Rolling frommain.TODO Checklist (to be completed in order)
mainbranches withrollingso 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.mdfiles 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.mainfor all repos before creatingironbranch. This will keepironpkgs always ahead ofhumbleand we can release API breaking features intoiron.ironbranch frommainon all repos.humbletorollinghumbleto matchrolling-> mergedrollingintohumbleand did a patch bump.humbletomainforrmf_utilshumbletomainfor rmf_visualization_msgsironhumblemainfor all repos so thatmainremains ahead ofiron.rollingironbranchiron-releasewith exact tags of release pkgsiron-releasewith date of update egrelease-iron-230526humblebranchhumble-releasewith exact tags of release pkgs: https://github.com/open-rmf/rmf/blob/humble-release/rmf.reposhumble-releasewith date of update egrelease-humble-230526rmf_devmetapackage