Autoware packages release from ROS buildfarm #4946
Labels
component:calibration
Calibration of sensors and hardware.
component:control
Vehicle control algorithms and mechanisms.
component:interfaces
Communication protocols, interfaces and messages.
component:launch
Launch files, scripts and initialization tools. (auto-assigned)
component:localization
Vehicle's position determination in its environment.
component:map
Map creation, storage, and loading.
component:perception
Advanced sensor data processing and environment understanding.
component:planning
Route planning, decision-making, and navigation.
component:sensing
Data acquisition from sensors, drivers, preprocessing.
component:simulation
Virtual environment setups and simulations.
component:system
System design and integration.
component:tools
Utility and debugging software.
component:vehicle
Vehicle-specific implementations, drivers, packages.
type:build
Tooling and infrastructure around building the Autoware.
type:ci
Continuous Integration (CI) processes and testing.
Checklist
Description
As I mentioned here https://github.com/orgs/autowarefoundation/discussions/4671, we will release the packages of Autoware that have been organized and version-controlled from the ROS buildfarm.
Purpose
By releasing from the ROS buildfarm, we can achieve thorough version control, reduce build times, and improve ease of Autoware setup.
Possible approaches
Execute the releasing procedure for each repository.
https://docs.ros.org/en/jazzy/How-To-Guides/Releasing/Releasing-a-Package.html
Definition of done
https://github.com/autowarefoundation/autoware_common.githttps://github.com/tier4/autoware_auto_msgs.gitThe text was updated successfully, but these errors were encountered: