Autonomy Software WG Meeting 2022/05/17 #2588
Replies: 0 comments 3 replies
-
@BonoloAWF @xmfcx cc @mitsudome-r Hi, I'd like to discuss the transition strategy from ROS 2 Galactic to Humble (at this meeting and also at the next TSC). I'll summarize the status (autowarefoundation/autoware.universe#268) into several slides, so I want to get feedback from Bus ODD members about their requirements for the transition. Thank you. 🙇 |
Beta Was this translation helpful? Give feedback.
-
I also have additional topic about having a monthly release of autoware for ease of testing. Comment from itri-bus channel in Discord.
|
Beta Was this translation helpful? Give feedback.
-
Administrative
Attendees
Chaired by Fatih
Common Resources
Announcements
Fatih created an S3 bucket for hosting Autoware files. The collected data will be kept in one place.
Autoware.Auto
Autoware.Universe
Discussion topics
Proposed by Kenji:
I'll summarize the status (Support rolling(humble) autoware.universe#268) into several slides, so I want to get feedback from Bus ODD members about their requirements for the transition.
For example, "When can the vehicle's OS be updated to 22.04?" in order to determine the support timeline.
Summary of the presentation from Ryohsuke:
Fatih(F) - does Galactic work in Ubuntu 22.04? Ryohsuke (R) - I'm not sure but you may need to install from source. F - I expect the transition to be short and maintenance support to be minimal given not many are using Universe in production. R - Yes. Engineers from TierIV will work on the Humble transition. Xinyu (X) - ROS has a new release every year so are we going to move to another release next year too? The migration will take half a year so it should only be done for significant improvements. R - LTS is released every 2 years and other releases are done annually. We have to move to Humble since Galactic is EOL. We don't see any critical features for Galactic to Humble so we can skip the next short term release if feature improvements are not significant.
Proposed by Ryohsuke:
The idea is that we will have a release branch in the https://github.com/autowarefoundation/autoware repository with a repos file pointing to a certain commit hash at certain point in time. We will run the CI against the branch to make sure that it doesn't have a build failure and also make sure that it passes a minimal set of driving scenarios using scenario simulator.
Ryohsuke (R) - we have been releasing at the end of each ODD project which is too slow for users who want to test Autoware. We should rather do monthly releases which will be more stable. Fatih (F) - most of the labour intensive part will be changing the .repos file to replace main with the actual commit hashes. Writing a script to automate this would be helpful. R - Yes, there is a function that can auto generate this. The naming could be as simple as 01beta, 02beta... F- a Github action script would have this. R - This would be monthly snapshot rather than monthly feature releases.
Proposed by Fatih:
Everyone to review the vehicle interface docs:
Action Items
Review of Issues and Discussions
The following Discussions and Issues were highlighted:
Beta Was this translation helpful? Give feedback.
All reactions