Migration Step for Planning Simulator-Specific Packages

[sasakisasaki]

Checklist

• I've read the contribution guidelines.
• I've searched other issues and no duplicate issues were found.
• I've agreed with the maintainers that I can plan this task.

Description

Provide a detailed procedure for planning simulator-related package-porting in the following Autoware Discussion.

Autoware Discussion

• https://github.com/orgs/autowarefoundation/discussions/6892

Repository for Ported Packages

• https://github.com/autowarefoundation/autoware_simple_planning_simulator/tree/separate-planning-simulator-dependency-from-autoware-universe

Purpose

Same as in the Autoware Discussion. But let me write the same one here too:

The purpose of this proposal is to discuss the possibility of extracting simulator-specific packages from autoware_universe into a separate repository, which can be used by both autoware_universe and autoware_core.

Possible approaches

Migration Plan

Same as the Autoware Discussion. But let me write here too.

• Create a new repository.
• Finish autoware_simulation_msgs porting
  • chore(autoware_simulation_msgs): ported from tier4_autoware_msgs autoware_msgs#162
• Refactor following packages that uses tier4_xxx_msgs (xxx = simulation, vehicle), so they use autoware_xxx_msgs
  • (tier4_simulation_msgs) autoware_dummy_perception_publisher
  • (tier4_vehicle_msgs) autoware_simple_planning_simulator
• Move packages listed above (and possibly more) with minimal changes.
• Update dependency references in autoware_universe and autoware_core.
• Verify build and simulation flows referenced in autoware_core README.

Definition of done

Finish all stuffs in the "Migration Plan".

[sasakisasaki]

@mitsudome-r Created the issue as we discussed in the Software Working Group 👍

[sasakisasaki]

Created a PR to use autoware_simulation_msgs for autoware_dummy_perception_publisher.

• refactor(dummy_perception_publisher): replace tier4_simulation_msgs by autoware_simulation_msgs #12499