Skip to content

Port tier4_planning_msgs to autoware_planning_msgs #114

@cyn-liu

Description

@cyn-liu

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

Hi @mitsudome-r @xmfcx @youtalk
In Autoware.Universe to Autoware.Core Porting Activity, it is required that each package can only use messages defined under AutowareFoundation GitHub Org (e.g., autoware_msgs and autoware_internal_msgs).

In order to accelerate the porting process, we will move all messages from tier4_planning_msgs to autoware_planning_msgs. Next, we will replace all tier4_planning_msgs in Autoware.Universe with autoware_planning_msgs.

If everyone has no objections, I will start this work in the next few days.

Purpose

  1. Move all still use messages from tier4_planning_msgs to autoware_planning_msgs.
  2. Replace all tier4_planning_msgs in Autoware.Universe with autoware_planning_msgs.

Possible approaches

None.

Definition of done

None.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions