This is a rough list of areas which are planned to be worked on in releases in the near future. This is not a full list and is intended to be used only as a rough guide and is subject to change. 2020 Q3 Concepts Use of Eclipse hawkBit for Apertis updates Addition of NTFS support for offline updates HMI Import of agl-compositor as a reference HMI Infrastructure Move project health checks from Jenkins to GitLab CI pipelines Evaluate need for further testing and monitoring of Apertis infrastructure Move tiny-image-recipe build pipeline from Jenkins to GitLab CI System Update Integration of Eclipse hawkBit as update option Q2 Concepts Integration of OP-TEE Automated OSS compliance Addition of exFAT support for offline updates Documentation Integrated search on www. [Read More]

Release Schedule

Apertis has a three month release cycle. Development happens through most of the cycle with emphasis on bug fixing towards the end. The quarterly release cycle was chosen as it fits well with the fast paced development of Apertis. Release timeline The Apertis release cycle starts at the end of the previous release cycle. At this point, new features are proposed, discussed and implemented. The soft feature freeze takes place about 4 weeks before the bug fixing stops. [Read More]

Hardware Enablement

This page documents what is required from hardware platform (and specifically the software interfaces used) to integrate well into Apertis. For Apertis to easily support a variety of hardware platforms, it is important that a consistent set of user space components can be used across the range of supported devices. To achieve this (in-line with its Upstream First strategy), Apertis relies on upstream interfaces and frameworks to access the hardware. Interfaces that aren't supported upstream (or cannot go upstream for whatever reason) require extra effort to support, test and maintain. [Read More]


Apertis is a free software project which is designed and developed in the open. The Apertis community is made up of both contributors who work to improve Apertis and users. Join the community The best ways to get in touch with the community are through: Mailing lists The devel mailing list is the place to discuss Apertis development and project If you are interested in adding a new mailing list, please contact listmaster at apertis. [Read More]


Apertis has a release lifecycle which is roughly three months long. Each release consists of a round of development, testing and bug fixing, followed by a stable release. Apertis also has a daily set of images which can be used for the latest testing. You can find: stable release images daily build images Apertis is actively developed, so you should always develop against either the latest release or the daily build images. [Read More]

Package maintenance

Apertis hosts its own package subset on the Apertis GitLab instance. On successful completion of the CI pipeline these are uploaded to Collabora's Open Build Service (OBS) instance where the packages are formally built and hosted for Apertis. Packages Guidelines The package set is distributed in several groups: target, development, sdk, hmi, helper-libs. Those groups are merged in a single repository, and split in what distribution names repository components (target, development, sdk, hmi, helper-libs). [Read More]

Marketing Resources

The Apertis Logo The Apertis logo consists of 2 elements: The Symbol The Wordmark In most situations the Symbol and the Workmark should remain connected and used as a whole. In isolated cases, where suitable, it is permitted that the Symbol can be separated from the Workmark, likewise the Wordmark can be removed from the Symbol. When using the Symbol and Wordmark togther, please ensure that you maintain the spacing /layout between them as below. [Read More]

About Apertis

Apertis is a FOSS (Free and open source) GNU/Linux-based platform tailored to the automotive needs and fit for a wide variety of electronic devices. It is a distribution derived from Debian/Ubuntu and geared towards the creation of product-specific images for ARM and Intel x86 systems. Apertis comes with a range of built-in features, which can be expanded upon with custom applications that are available through an App Store. It is not intended to support mission-critical features in vehicles (such as steering, brakes, engine control, etc. [Read More]

Code of Conduct

This text documents what you can expect from the Apertis community online and at events and, in turn, what we expect from you. We believe that people generally mean well. Excepting strong evidence to the contrary, we ask that you do the same. We favour communication over confrontation. Most issues that arise during day-to-day contribution to any software project and at events can be resolved by communication between the affected parties. [Read More]