Skip to content
This repository was archived by the owner on Sep 15, 2025. It is now read-only.
This repository was archived by the owner on Sep 15, 2025. It is now read-only.

Change software development process #75

Description

@JanStaschulat

Change software development process in micro-ros/rclc repository.

Prolem:

  • ros2/rclc and micro-ros/rclc repositories have to be kept in-sync.
  • issues can be created on ros2 as well as micro-ros repo
  • duplicate merge of micro-ros features branches
    • first from micro-ros/rclc:feature-branch to micro-ros/rclc:master and,
    • secondly, from micro-ros/rclc:master to ros2/rclc:master
  • creation of bloom release from ros2/rclc involves bumping version, this change needs to be pulled back to micro-ros/rclcfork.

New software development process:

  • the micro-ros/rclc:master branch will be deleted
  • new feature branches in micro-ros/rclc repository shall be created from ros2/rclc:master
  • pull requests shall be created to ros2/rclc:master

Benefits:

TODO:

  • resolve all errors due to bloom releases on ros2/rclc
  • close or transfer all open issues to ros2/rclc:issues
  • keep all feature branches at micro-ros/rclc => they need to be re-based to ros2/rclc later
  • merge or close all open pull requests on micro-ros/rclc
  • make a pull from ros2/rclc to micro-ros/rclc
  • update scripts in micro-ros repositories : replace miro-ros/rclc:master to ros2/rclc:master (Pablo)
  • rename micro-ros/rclc:master to micro-ros/rclc:master-depricated
  • change default branch to micro-ros/rclc:main
  • delete micro-ros/rclc:master-depricated
  • inform community (presented in embedded working group on 03/03/2021)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions