Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port tier4_planning_msgs to autoware_planning_msgs #114

Open
3 tasks done
cyn-liu opened this issue Dec 23, 2024 · 0 comments
Open
3 tasks done

Port tier4_planning_msgs to autoware_planning_msgs #114

cyn-liu opened this issue Dec 23, 2024 · 0 comments

Comments

@cyn-liu
Copy link

cyn-liu commented Dec 23, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant