This issue reports all repos involved in foxy migration and details the future requirements for each of them.
micro-ROS Foxy migration is compound of multiple repos with feature/foxy_migration branches that must be merged into a final foxy branch on each of them:
Before release every row must have a PR merged from feature/foxy_migration to foxy
Related PR, should be merged before release procedure:
NOTES:
-
https://github.com/eProsima/crazyflie-clients-python should be a standalone CF Radio to micro-ROS Agent bridge with installation instructions: WIP
-
All feature/foxy_migration branches are referenced from this micro-ROS Build System repo. The last pre-release commits must change all these branches from feature/foxy_migration to foxy
POST RELEASE:
This issue reports all repos involved in foxy migration and details the future requirements for each of them.
micro-ROS Foxy migration is compound of multiple repos with
feature/foxy_migrationbranches that must be merged into a finalfoxybranch on each of them:Before release every row must have a PR merged from
feature/foxy_migrationtofoxyRelated PR, should be merged before release procedure:
NOTES:
https://github.com/eProsima/crazyflie-clients-python should be a standalone CF Radio to micro-ROS Agent bridge with installation instructions: WIP
All
feature/foxy_migrationbranches are referenced from this micro-ROS Build System repo. The last pre-release commits must change all these branches fromfeature/foxy_migrationtofoxyPOST RELEASE:
rcutilsrepository HEAD commit has changed in origin ros2 repository since the moment it was forked. A further revision of the last introduced changes must be done before rebasing this repository to ros2:foxy branch.