-
Zygmunt Krynicki authored
Signed-off-by:Zygmunt Krynicki <zygmunt.krynicki@huawei.com>
Zygmunt Krynicki authoredSigned-off-by:
Aladeen - 0.1.0
About
The objective of this document is to provide basic introductory information about included functionalities, known issues, instructions guidance for the Aladeen release of the |main_project_name| project.
The |main_project_name| project is meant to serve as a solid base foundation for products. It is not a standalone product itelf, but rather a starting project for other projects and products.
Scope
Release codename: Aladeen
Release version: 0.1.0
Release timeframe: 2020/11/15 .. 2021/04/12
The objectives of the release
The purpose of this release is to provide the European |main_project_name| project with a set of initial functionalities after the first code release in September, 2020. This April release serves as a solid foundation upon which we can share the entire 2021 roadmap of the project.
More details on the |main_project_name| goals can be found in the :doc:`/overview/allscenarios-vision` document.
The list of software features included
| Functionalities | Area |
|---|---|
| Bitbake build infrastructure | Build tools |
| Continuous IP compliance and Openchain IP policy | FOSS compliance |
| Linux 5.10 | Kernel |
| Zephyr 2.5 | Kernel |
| FreeRTOS (experimental) | Kernel |
| GCC / LLVM cross toolchains | Toolchain |
| gdb / gdbserver debugging | Tools |
| Qemu targets for Intel and ARM | Simulators |
| Build flavors and base / extra root fs images | Build tools and root fs |
| Smart Panel Blueprint | Reference Blueprint |
| Continuous IP compliance and Openchain IP policy | FOSS compliance |
| Release Bill of Material and FOSS compliance dashboard | FOSS compliance |
| Application Compatibility Test Suite | Testing and compatibility |
| CI / CD pipelines and DevSecOps public cloud infrastructure | DevSecOps |
| Web portal and communication assets including Twitch channel | Marcom |
| Automated sphinx-based documentation pipeline | Documentation |
Supported hardware platforms
| Board (chipset) | Supported kernels | Board documentation |
|---|---|---|
| Nitrogen (nRF52832 - Cortex-M4) | Zephyr | :ref:`SupportedBoardNitrogen` |
| Avenger96 (STM32 - Cortex-A7 & Cortex-M4) | Linux & Zephyr | :ref:`SupportedBoardAvenger96` |
| SBC-C61 (NXP i.MX 8M - Coretex-A53 & Cortex M4) | Linux | :ref:`SupportedBoardSecoC61` |
| SBC-B68-eNUC (Intel x86) | Linux | :ref:`SupportedBoardSecoB68` |
Test report
Not available for this release.
Installation
:ref:`Quick Build <AllscenariOSQuickBuild>` provides an example of how to build the |main_project_name| project for a supported target. Visit the :ref:`Hardware Support <HardwareSupport>` section for instructions on how to build for other supported targets.
Visit :ref:`setting up a repo workspace <RepoWorkspace>` for general instruction while using the release tag for the repo init commands as follows:
repo init -u https://git.ostc-eu.org/OSTC/OHOS/manifest.git -b refs/tags/v0.1.0Known issues
The Avenger96 target (stm32mp1-av96) does not ship with firmware files for Bluetooth, Wifi and the image processor by default. We are working on a solution to re-distribute them during the normal image builds for this board.
Source code available
For more details on our repo structure, see:
OSTC group at GitLab document
Devops infrastructure
To learn more about our approach to CI (Continuous Integration) strategy used for this release, please see:
:doc:`/ci/index` document
Testing
For more details please refer to:
:doc:`/ci/xts-acts` document
Contributions
If you are a developer eager to know more details about |main_project_name| or just an enthusiast with a patch proposal, you are welcome to participate to our |main_project_name| ecosystem development. To do so, please sign-up using the process described below:
:doc:`/contributing/index` document
License
Project manifest as well as project-specific meta-layers, recipes and software packages are, unless specified otherwise, published under Apache 2.0 license. The whole operating system built by users from the project manifest is an aggregate comprised of many third-party components or component groups, each subject to its own license conditions.
Official project release includes only the project manifest as well as project-specific meta-layers, recipes. Any reference binary image, build cache and any other build artifacts are distributed as a convenience only and are not part of the release itself.