[Release] 1.10.0

[kfunaoka]

Status

PRODUCTION

Description

Release v1.10.0 (#1682)

Related PRs

branch	PR
release/1.10.0 to develop	#1901

Todos

• Update CHANGELOGs
• Update Package Versions
• Fix CUDA problem (#1906)
• Replace License in package.xml ([Release] 1.10.0 #1898 (comment))
• Decide the direction that merge back to develop

[amc-nu]

change license string to Apache in all the Autoware packages.

[kfunaoka]

Wow. Should the package.xmls outside Autoware/ros/src/sensing/drivers/ be changed?

I've also faced the following error at launching YOLO3 via autoware/autoware:1.10.0-kinetic-rc1.

CUDA Error: CUDA driver version is insufficient for CUDA runtime version

Should I update something?

• In host PC:

$ cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.54  Tue Aug 14 19:02:34 PDT 2018
GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10)

$ /usr/local/cuda-9.2/bin/nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2018 NVIDIA Corporation
Built on Tue_Jun_12_23:07:04_CDT_2018
Cuda compilation tools, release 9.2, V9.2.148

• In autoware/autoware:1.10.0-kinetic-rc1:

$ nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2017 NVIDIA Corporation
Built on Fri_Sep__1_21:08:03_CDT_2017
Cuda compilation tools, release 9.0, V9.0.176

[kfunaoka]

@esteve @amc-nu @sgermanserrano How about merging the following sequence:

1. [Release] 1.10.0 #1898 to master (this pull request)
2. [Release] 1.10.0 merged back to develop #1901 to develop
3. [DO NOT MERGE YET][Fix] Revert b21b663 #1902 to develop once all install targets are confirmed to work fine

Or any other suggestion?

I think #1901 is mandatory so that the CHANGELOGs are generated correctly at next release v1.10.1 or v1.11.0. If #1901 is not merged, catkin_generate_changelog can not distinguish between which commits are v1.10.0 and which commits are next release.

[amc-nu]

From @alexandrx

Regarding @amc-nu comment before, you can easily check:
for I in `find <AUTOWARE-PATH> -type f -name "package.xml"`; do grep -i "<license" -H $I; done | grep BSD | wc -l
there are 127 different packages stating <license>BSD</license>.
Change the last part grep BSD by grep -i apache and there are only 5 packages stating Apache, and from those 5 only one package says "Apache 2". There are also some "TODO" licenses, 1 "gpl" and 1 "nonstandard".
As you know, you can fix all the package.xml files with the following trivial script:
for I in `find <AUTOWARE-PATH> -type f -name "package.xml"`; do sed -i 's/<license>BSD/<license>Apache 2.0/g' $I; done
(just in case)

[kfunaoka]

Before doing that, we need to distinguish which packages can be Apache2 :)

My suggestion at the issue is that drivers can not be changed to Apache2 in my understanding.

Are there any other comments?

[kfunaoka]

Thanks, @amc-nu !
He gave me the list that was all implemented as Autoware project.

• baumer
• pointgrey
• vectacam
• javad_navsat
• nmea_navsat
• memsic
• hexacam
• ouster

[amc-nu]

@kfunaoka Another item for the TODO list:

• Change license in README and LICENSE file