1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
meta-ivi, the Yocto layer for In-Vehicle Infotainment
=====================================================
This layer's purpose is to add In-Vehicle Infotainment (IVI) support when
used with Poky. The goal is to make the Yocto Project reference system
Poky GENIVI compliant.
Branch Policy
-------------
- New development is done on **master** branch and most new change requests
(PRs) should be proposed as changes to master, unless you know they are
applicable to a particular release only.
- In general, prefer a linear commit history (rebase and cherry-pick),
applying merge commits only where absolutely necessary to sort out a
complex merge situation (which we should rarely have).
- The maintainer shall ensure that relevant patches are cherry-picked to
every branch where they apply. I.e. patches should be back-ported *at
minimum* to the Support Window versions, as defined below.
- Meta-ivi uses [semantic versioning](http://semver.org/).
- The release schedule is driven by a time plan.
- The GENIVI Compliance Specification is released annually, while meta-ivi is
released twice a year. Major numbers follow the compliance specification.
E.g. We will create 14.x-rocko branch together with the specification
14.0.0 and 14.x-sumo half way to 15.0.0.
- Meta-ivi updates regularly to follow Yocto/Poky releases.
- Somewhere near a new major release of the specification, a numbered
release branch (e.g. 14.x-rocko and 14.x-sumo) is created from master, and
the new branch goes into stabilization/release phase.
- In the middle between the specification version 14.0 and 15.0 a numbered
branch is created for the 14.x-sumo meta-ivi release.
- After a versioned release, the release branch remains for maintenance and
updates.
Tag Policy
----------
- Meta-ivi creates tags, in accordance with semver. Major numbers follow
the GENIVI Compliance Specification. Examples: 14.0.0, 14.0.1, 14.1.0
- Releases are created from the respective working branch.
- GitHub releases are also created.
- When layer upgrades are done, version numbers will be as follows:
- The versions used on 14.x-rocko will start at 14.0.0.
- The versions used on 14.x-sumo will start on 14.50.0 to keep the major version
numbers in sync.
- Note: Updates to the 14.0.0 release would then become 14.0.1 and/or 14.1.0,
which can be released __after__ 14.50.0.
- Tags of the type P-0.1, P-0.2 etc, are internal tags used for some
prereleases.
Support Window (Bugfixes, improvements)
---------------------------------------
- Because of available resources, and often low engagement from those companies
that have settled on a version and gone into a production project, support
is given for only the most recently released version, and *one* version
before it.
Support Window (Security)
-------------------------
- If critical security fixes are identified, the maintainer should apply
them (if applicable) to the most recently released version and *two*
versions before it.
**Note** however that there is currently no quantified or documented
commitment to tracking CVEs, nor any guarantee to apply all possible
security fixes. While it is of course tracked to the best of the
maintainer's ability, the project is dependent on community input. All the
_responsibility remains on the adopting companies_ to secure their final
products.
Contribution
-------------
The meta-ivi project welcomes contributions. You can contribute code,
submit patches, report bugs, answer questions on our mailing lists and
review and edit our documentation and much more.
[Wiki page](https://at.projects.genivi.org/wiki/display/PROJ/meta-ivi).
[Mailing list](https://lists.genivi.org/mailman/listinfo/genivi-meta-ivi_lists.genivi.org)
[report Bugs](https://at.projects.genivi.org/jira/projects/BASE/).
Please see the
[MAINTAINERS](https://github.com/GENIVI/meta-ivi/blob/master/MAINTAINERS)
file for information on contacting the maintainers
of this layer, as well as instructions for submitting patches.
Subscribe to the mailing list
[here](https://lists.genivi.org/mailman/listinfo/genivi-meta-ivi).
[View or Report bugs](https://at.projects.genivi.org/jira/secure/RapidBoard.jspa?rapidView=10&projectKey=BASE).
Read the [wiki](https://at.projects.genivi.org/wiki/display/PROJ/meta-ivi).
For information about the Yocto Project, see the
[Yocto Project website](https://www.yoctoproject.org).
For information about the Yocto GENIVI Baseline, see the
[Yocto GENIVI Baseline wiki](https://at.projects.genivi.org/wiki/display/PROJ/GENIVI+Baselines).
Layer Dependencies
------------------
URI: git://git.yoctoproject.org/poky
> branch: thud
> revision: 4046716c2f315308048d568e5b606382ef7bc38b
URI: git://git.openembedded.org/meta-openembedded
> layer: meta-oe
> branch: thud
> revision: f1511d254632a34c1deb51f4bf8b8c21e7423f51
URI: git://git.yoctoproject.org/meta-gplv2
> branch: thud
> revision: 379ea8dd144b06aeb459e9a82c792c84d8a5baf7
Using the above git SHAs and the master meta-ivi branch,
bitbaking pulsar-image is known to work
(the pulsar-image build should be aligned with GENIVI 14.0).
For creating a specific GENIVI compliant image version, please make sure you
git checkout the related meta-ivi branch and follow the build instructions
located in the README.md file of that branch. So for example, to build
an image that should be GENIVI 9.0 compliant, checkout the meta-ivi 9.0 branch,
and follow the README.md part of that branch. As does the GENIVI Alliance
we only support the current and the previous version. Any version older
than that is not supported any more, and therefore may not build or run.
Supported Machines
------------------
We do smoke test the builds of the three supported machines:
* QEMU (IA-32) - emulated machine: qemux86
* QEMU (x86-64) - emulated machine: qemux86-64
* QEMU (ARM64) - emulated machine: qemuarm64
Adaptation and testing with other hardware BSPs is typically done by other
community projects like the GENIVI Development Platform, and by product
companies.
Please check on our [wiki](https://at.projects.genivi.org/wiki/display/PROJ/meta-ivi)
regarding any community supported machines.
For example there Renesas provides a public Board Support Package (BSP)
available for use with meta-ivi.
|