The timeline for the change from autoware_auto_msgs to autoware_msgs

[yukkysaito]

Related link :

• https://github.com/orgs/autowarefoundation/discussions/3668
• https://github.com/orgs/autowarefoundation/discussions/3862

Timeline :

• work-branch : feature/autoware-msgs
• Implementation timeline : Nov. 30th, 2023
  • Test: planning simulator (tutorial), logging simulator (tutorial)
• period of transition (e.g. from old to new system) :Jan. 31st, 2024 (2 month)
  • PullRequests to the main branch will be allowed during this period. If maintenance is too difficult, we will consider it again.
  • Synchronization between main and feature/autoware-msgs will be done once a week.

[mitsudome-r]

I have discussed about the progress with AutoCore on this topic.
They are now finishing the porting in autoware_msgs branch in Autoware.Universe, and they will also create the autoware_msgs in autoware repository next week to test if it works with planning simulator.
Therefore there will be a week delay from the schedule that @yukkysaito originally posted.

[yukkysaito]

related issue : #4104

[yukkysaito]

@mitsudome-r Can you share your current status?

[mitsudome-r]

It seems like they were able to sync with with the main branch from the end of December. They have tested planning_simulation and make sure that it can drive a simple path.
We are currently trying to extend the contract with AutoCore so that we can resume syncing the branch weekly (Maybe from the next week)

[kielczykowski-rai]

@mitsudome-r
I wanted to bump the thread. I would like to know the scope of incoming work in autoware_msgs and autoware_internal_msgs repository and the estimated timeline for the end of work.

Context: migrating scenario_simulator_v2 to autoware_msgs

[mitsudome-r]

autoware_msgs will be the message defined in Autoware Design and will be the messages used commonly between Autoware Core and Universe. On the other hand, autoware_internal_msgs are the messages that contains other optional messages such as debug messages.

[mitsudome-r]

autoware_internal_msgs are meant to be only used in Autoware repository since they are not official main interface so if you are migrating scenario_simulator_v2, it shouldn't be relying on autoware_internal_msgs

[mitsudome-r]

We plan to finish testing in March

[xmfcx]

autowarefoundation/autoware.universe@main...autoware_msg