| Roberto Perez | d18be35 | 2019-08-12 18:25:57 -0700 | [diff] [blame] | 1 | # Android Automotive 'Chassis' library |
| 2 | Components and resources designed to increase Automotive UI consistency between |
| 3 | GAS (Google Automotive Services) apps, system-apps and OEM developed apps. |
| 4 | |
| Brad Stenning | 667accc | 2019-09-13 09:55:18 -0700 | [diff] [blame] | 5 | See: go/aae-carui |
| Roberto Perez | d18be35 | 2019-08-12 18:25:57 -0700 | [diff] [blame] | 6 | |
| 7 | ## Content |
| 8 | |
| 9 | Components and resources designed to be configured by means of RRO (Runtime |
| 10 | Resource Overlays) by OEMs. |
| 11 | |
| 12 | ## Updating |
| 13 | |
| 14 | This library is developed in Gerrit and copied as source to Google3 using |
| 15 | Copybara (go/copybara). |
| 16 | |
| Brad Stenning | 68821a8 | 2019-09-16 10:06:04 -0700 | [diff] [blame] | 17 | Source: /packages/apps/Car/libs/car-ui-lib |
| Roberto Perez | d18be35 | 2019-08-12 18:25:57 -0700 | [diff] [blame] | 18 | Target: //google3/third_party/java/android_libs/android_car_chassis_lib |
| 19 | |
| 20 | Here is the process for updating this library: |
| 21 | |
| Roberto Perez | 9451382 | 2019-08-26 17:25:14 -0700 | [diff] [blame] | 22 | 1. Develop, test and upload changes to Gerrit |
| 23 | 2. On Google3, run './update.sh review <cl>' (with <cl> being your Gerrit CL #) and test your changes |
| 24 | 3. Repeat #1 and #2 until your changes look okay on both places. |
| 25 | 4. Back on Gerrit, submit your CL. |
| 26 | 5. Back on Google3, run './update.sh manual' submit |
| Roberto Perez | d18be35 | 2019-08-12 18:25:57 -0700 | [diff] [blame] | 27 | |
| Roberto Perez | 62d4cfb | 2019-08-16 17:06:04 -0700 | [diff] [blame] | 28 | TODO: Automate this process using CaaS (in progress) |
