diff --git a/releases/2.0/2.0.0/index.rst b/releases/2.0/2.0.0/index.rst
new file mode 100644
index 0000000000000000000000000000000000000000..819668b5bdebb8b86ece200e3ba8d0d77012019e
--- /dev/null
+++ b/releases/2.0/2.0.0/index.rst
@@ -0,0 +1,27 @@
+.. SPDX-FileCopyrightText: Huawei Inc.
+..
+.. SPDX-License-Identifier: CC-BY-4.0
+
+.. include:: ../../../definitions.rst
+
+2.0.0
+#####
+
+**Release timeframe**: 2022-03-07 .. 2022-11-30
+
+**Release Artefacts Download Area**: https://download.eclipse.org/oniro-core/releases/2.0.0/
+
+**Release Tags GPG Public Key**: https://download.eclipse.org/oniro-core/releases/2.0.0/oniro-2.0.0_gpg_key.asc [*]_
+
+.. toctree::
+ :maxdepth: 1
+
+ release_notes
+ requirements
+ test_report
+ ip_compliance_note
+ security_report
+
+.. [*] All repositories released part of 2.0.0 have associated 2.0.0 `git
+ tags` that have been signed during the Eclipse Foundation release process.
+ You can use this GPG public key to verify all these signatures.
diff --git a/releases/2.0/2.0.0/ip_compliance_note.rst b/releases/2.0/2.0.0/ip_compliance_note.rst
new file mode 100644
index 0000000000000000000000000000000000000000..8b025adbadad63f3fa33310b547923f83a589e6a
--- /dev/null
+++ b/releases/2.0/2.0.0/ip_compliance_note.rst
@@ -0,0 +1,285 @@
+.. SPDX-FileCopyrightText: Alberto Pianon <pianon@array.eu> and Carlo Piana <piana@array.eu>
+..
+.. SPDX-License-Identifier: CC-BY-4.0
+
+.. _2_0_0_IPComplianceNote:
+
+IP Compliance Note
+==================
+
+Since the very beginning, a Continuous Compliance `toolchain`_ and `process`_
+have been developed and integrated into the Oniro project development so that
+source components used to generate Oniro binary images are continuously scanned
+by open-source tools like `Fossology`_ and `Scancode`_, and reviewed by
+Software Audit Experts and IP Lawyers [*]_.
+
+For detailed information about the why and the how of such a process, please
+refer to the Oniro Compliance Toolchain’s `official documentation`_. Sources
+and documentation for custom components of the toolchain (`tinfoilhat`_,
+`aliens4friends`_, `dashboard`_, `pipelines`_) can be found in their respective
+repositories.
+
+*TL;DR*: we put ourselves in your shoes, a device maker willing to use Oniro to
+develop its products. We simulated the IP compliance work you would have to do
+(on third-party components fetched by Yocto recipes) to build your firmware
+image(-s) and spot possible legal risks and issues. In the true open-source
+spirit, every time we found an issue with a particular upstream component, we
+raised that issue upstream, and most of the time we got it solved for you by
+upstream developers.
+
+As of Oniro’s 2.0.0 GA Release, there are just a few issues left that we cannot
+address. These relate to proprietary firmware/drivers for hardware support and
+some patent-covered technologies. The issues require your attention and
+possible action, e.g. getting a patent license. We will briefly explain these
+here.
+
+The overall status of audit activities can be monitored through a `dedicated
+dashboard`_, which gets updated after every commit to Oniro's main repository.
+In the dashboard, also CVE information (collected at the time of the commit) is
+shown and can be filtered based on target machines, images, and single
+components.
+
+All repositories included in the Oniro 2.0.0 Release are `REUSE compliant
+<https://reuse.software/spec/>`_. It means that copyright and license metadata
+for every source file are made available within each repository in a standard
+machine-readable format, and that at any time one can generate an SPDX SBoM
+[*]_ for such repositories with `REUSE tool
+<https://github.com/fsfe/reuse-tool>`_ by just running ``reuse spdx`` command.
+REUSE-generated SPDX files for all released repositories are available as part
+of the `release artefacts download area
+<https://download.eclipse.org/oniro-core/releases/oniro-v2.0.0_spdx_sbom.tar.gz>`_.
+
+Last but not least, we provide reference SPDX SBoM of source packages used to
+build oniro-image-base and zephyr-philosophers images for a selection of
+supported target machines (qemu, raspberrypi4, arduino-nano-33ble), generated
+by continuous compliance pipelines. They are provided as a convenience only,
+with no express or implied warranty about the accuracy and completeness of the
+information contained therein (see the disclaimers below):
+
+============================= ====== ============ =================== ===================
+SBoM kernel toolchain(s) machine(s) image
+============================= ====== ============ =================== ===================
+`linux-qemu`_ linux gcc,clang qemu\* oniro-image-base
+`linux-raspberrypi4`_ linux gcc,clang raspberrypi4-64 oniro-image-base
+`zephyr-qemu`_ zephyr gcc qemu\* zephyr-philosophers
+`zephyr-arduino-nano-33-ble`_ zephyr gcc arduino-nano-33-ble zephyr-philosophers
+============================= ====== ============ =================== ===================
+
+.. _linux-qemu: https://download.eclipse.org/oniro-core/releases/2.0.0/oniro-v2.0.0_linux-qemu_images_spdx_sbom.zip
+.. _linux-raspberrypi4: https://download.eclipse.org/oniro-core/releases/2.0.0/oniro-v2.0.0_linux-raspberrypi4_images_spdx_sbom.zip
+.. _zephyr-qemu: https://download.eclipse.org/oniro-core/releases/2.0.0/oniro-v2.0.0_zephyr-qemu_images_spdx_sbom.zip
+.. _zephyr-arduino-nano-33-ble: https://download.eclipse.org/oniro-core/releases/2.0.0/oniro-v2.0.0_zephyr-arduino-nano-33-ble_images_spdx_sbom.zip
+
+*Disclaimer#1*: This is not legal advice. This note is provided just as a
+convenience for you, to suggest some critical areas in which you should seek
+legal advice if you want to develop real-world products based on Oniro. It is
+not meant to be complete nor to substitute internal due-diligence activities
+you need to perform before marketing your products.
+
+*Disclaimer#2*: This note covers only source components used to generate
+supported Oniro images (oniro-image-base and zephyr-philosophers) for supported
+target machines (qemux86-64, qemux86, qemuarm-efi, qemuarm64-efi,
+raspberrypi4-64, seco-intel-b68, seco-px30-d23, seco-imx8mm-c61-2gb,
+seco-imx8mm-c61-4gb, qemu-cortex-m3, nrf52840dk-nrf52840, arduino-nano-33-ble).
+
+*Disclaimer#3*: “supported†*referred to a board* means that a board is
+officially targeted as a potential platform where an Oniro image can be
+installed for any purposes; when *referred to an image*, means that the image
+targeting a supported board receives thorough testing and specific attention
+during the development. It does NOT mean that both will receive support
+services nor that any member of the Oniro Working Group or of the Eclipse
+Foundation will provide any warranty whatsoever.
+
+Solved Issues
+-------------
+
+- There was a proprietary software font accidentally included in
+ zephyr-philosophers; we opened the issue upstream
+ (https://github.com/zephyrproject-rtos/zephyr/issues/48111), which was
+ solved (https://github.com/zephyrproject-rtos/zephyr/pull/49103), and the
+ fix was backported to Oniro.
+ (https://gitlab.eclipse.org/eclipse/oniro-core/meta-zephyr/-/commit/0f36ae849d59da08e445af83f711a1c0108dd3bf);
+
+- A similar issue was found also in Harfbuzz component, raised upstream
+ (https://github.com/harfbuzz/harfbuzz/issues/3845), fixed
+ (https://github.com/harfbuzz/harfbuzz/pull/3846), and the fix was backported
+ to Oniro
+ (https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/commit/fbb4bc229b287fa293439ee0adbb0d830764b2d8).
+
+- There were a lot of binary files found in zephyr-philosophers, without
+ corresponding sources and no clear license information; we opened the issue
+ upstream
+ (https://gitlab.eclipse.org/eclipse/oniro-core/meta-zephyr/-/commit/0f36ae849d59da08e445af83f711a1c0108dd3bf),
+ which was then fixed
+ (https://github.com/zephyrproject-rtos/zephyr/pull/47181), and the fix was
+ backported to Oniro.
+ (https://gitlab.eclipse.org/eclipse/oniro-core/meta-zephyr/-/commit/a00d1c4f1aad8b0ea5b9f904966c0bd8a48d8d80)
+
+- Some proprietary license headers, not granting redistribution nor any other
+ rights without written permission by Intel, were found in some source files
+ in the Intel-Media-SDK component; we opened the issue upstream
+ (https://github.com/Intel-Media-SDK/MediaSDK/issues/2937) and it turned out
+ it was an oversight occurred when open sourcing the component; it was then
+ fixed (https://github.com/Intel-Media-SDK/MediaSDK/pull/2939) and the fix was
+ backported to Oniro.
+ (https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/commit/d5ee837d90903d91a1ff358ebfe985d28925484e);
+
+- A similar issue was found also in the Intel-Media-Driver component, it was
+ raised upstream (https://github.com/intel/media-driver/issues/1460), fixed
+ (https://github.com/intel/media-driver/pull/1465), and the fix was backported
+ to Oniro
+ (https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/commit/b56de944568c8e348cb8265c59d7cfd52a0831b9)
+
+Warnings for Downstream Users: Hardware Support
+-----------------------------------------------
+
+Linux
+~~~~~
+
+IMX Firmware
+^^^^^^^^^^^^
+
+A couple of supported target boards (seco-imx8mm-c61-2gb and
+seco-imx8mm-c61-4gb) require Freescale i.MX firmware for VPU and SDMA as well
+as firmware for 8M Mini family to train memory interface on SoC and DRAM during
+initialization. These firmware require acceptance of a `EULA`_ by the user
+(you). Such acceptance may be provided by flagging a specific environment
+variable (``ACCEPT_FSL_EULA = "1"``) in your configuration file (please refer
+to Oniro’s technical documentation). You should carefully read that `EULA`_ to
+check whether you are actually in a position to accept it and whether you can
+fulfill all of its conditions. If needed, seek legal advice for that.
+
+Linux-firmware
+^^^^^^^^^^^^^^
+
+The third-party components ``linux-firmware`` and ``linux-firmware-rpidistro``
+contain many sub-components (mainly firmware BLOBs) for specific hardware
+support, coming from different hardware vendors.
+
+Almost all firmware vendor licenses restrict firmware usage to the specific
+device(s) of their own.
+
+Some of them (apparently) contain further restrictions, stating that the binary
+file is licensed *“for use with [vendor] devices, but not as a part of the
+Linux kernel or in any other form which would require these files themselves to
+be covered by the terms of the GNU General Public Licenseâ€*. Our understanding
+is that such restriction is either redundant or useless. Apart from some
+debatable and contested corner cases, there is no way in which a firmware blob
+may become part of the Linux kernel and therefore be covered by the GNU General
+Public License - so the above provision seems redundant. But even if someone
+claimed that a proprietary firmware requires such a low-level interaction with
+the kernel that such firmware must be deemed as a derivative work of the kernel
+itself, such (alleged) non-compliance with GPL could not be avoided or excluded
+by a vendor license clause - so the above provision would be useless. You
+should seek legal advice to use the affected firmware files in either case.
+
+================================= ================================================== ======================== ============================
+Source Device/driver File(s) License found in
+================================= ================================================== ======================== ============================
+`linux-firmware-20220913.tar.xz`_ Conexant Cx23100/101/102 USB broadcast A/V decoder v4l-cx231xx-avcore-01.fw WHENCE
+`linux-firmware-20220913.tar.xz`_ meson-vdec - Amlogic video decoder meson/vdec/\* LICENSE.amlogic_vdec, WHENCE
+`linux-firmware-20220913.tar.xz`_ lt9611uxc - Lontium DSI to HDMI bridge lt9611uxc_fw.bin LICENSE.Lontium, WHENCE
+================================= ================================================== ======================== ============================
+
+Some other firmware files are covered by proprietary licenses that contain
+termination clauses providing that either party may terminate the license at
+any time without cause, which may work as killswitches (i.e. vendor may
+terminate your license at any time without any reason, so your devices -
+including already distributed ones - may lose, say, Bluetooth or Wifi support).
+You should seek legal advice (and possibly negotiate a different license with
+the vendor) if you need to use the affected firmware files:
+
+========================================================== ====================== ======== ================
+Source Device/driver File(s) License found in
+========================================================== ====================== ======== ================
+[git://github.com/murata-wireless/cyw-fmac-fw@ba140e42] Murata Wi-Fi/Bluetooth cyfmac\* LICENCE, README
+[git://github.com/murata-wireless/cyw-fmac-nvram@8710e74e] Murata Wi-Fi/Bluetooth cyfmac\* LICENCE.cypress
+[git://github.com/murata-wireless/cyw-bt-patch@9d040c25] Broadcom BCM43455 Wifi \*.hcd LICENCE.cypress
+========================================================== ====================== ======== ================
+
+Some other firmware files (for NVIDIA hardware, that is not included in any of
+Oniro’s supported boards) have been expressly excluded from installation
+because they come with a proprietary license with an unclear “open source
+exceptionâ€. See `issue #834`_ in Oniro main repo for further details.
+
+Some other firmware files are covered by a limited patent license. If you need
+to use them, you should check whether you fulfill the conditions of such a
+license.
+
+================================= ========================= ============================= ======================
+Source Device/driver File(s) License found in
+================================= ========================= ============================= ======================
+`linux-firmware-20220913.tar.xz`_ WiLink4 chips WLAN driver ti-connectivity/wl1251-fw.bin LICENCE.wl1251, WHENCE
+================================= ========================= ============================= ======================
+
+Finally, some licenses have unclear license wording about use and
+redistribution. If you need to use firmware covered by such files, you should
+check and possibly seek legal advice.
+
+================================= ===================================================== ================================== =======================
+Source Device/driver File(s) License found in
+================================= ===================================================== ================================== =======================
+`linux-firmware-20220913.tar.xz`_ WiLink4 chips WLAN driver ti-connectivity/wl1251-fw.bin LICENCE.wl1251, WHENCE
+`linux-firmware-20220913.tar.xz`_ Marvell Libertas 802.11b/g cards libertas/\*.bin, mrvk/\*.bin LICENCE.Marvell, WHENCE
+`linux-firmware-20220913.tar.xz`_ Marvell mac80211 driver for 80211ac cards mwlwifi/\*.bin LICENCE.Marvell, WHENCE
+`linux-firmware-20220913.tar.xz`_ Marvell CPT driver mrvl/cpt01/\* LICENCE.Marvell, WHENCE
+`linux-firmware-20220913.tar.xz`_ Marvell driver for Prestera family ASIC devices mrvl/prestera/\*.img LICENCE.Marvell, WHENCE
+`linux-firmware-20220913.tar.xz`_ wave5 - Chips&Media, Inc. video codec driver cnm/wave521c_j721s2_codec_fw.bin LICENCE.cnm, WHENCE
+`linux-firmware-20220913.tar.xz`_ Broadcom 802.11n fullmac wireless LAN driver brcm/brcmfmac/\*, cypress/cyfmac\* LICENCE.cypress, WHENCE
+`linux-firmware-20220913.tar.xz`_ BCM-0bb4-0306 Cypress Bluetooth firmware for HTC Vive brcm/BCM-0bb4-0306.hcd LICENCE.cypress, WHENCE
+================================= ===================================================== ================================== =======================
+
+Zephyr
+~~~~~~
+
+The third-party repository ‘`zephyr-philosophers`_’ fetched by
+zephyr-philosophers recipe contains many sub-components for specific hardware
+support, coming from different hardware vendors. Some of them have specific
+proprietary license conditions (eg. software components to support Atmel SAM
+L21, Altera Nios II, Cypress/Infineon PSoC6) but are not used to generate Oniro
+images, so they are not covered here. Should you need to add support for such
+hardware boards, not officially supported by Oniro, you should carefully check
+hardware vendor's license conditions.
+
+Warnings for Downstream Users: Patents
+--------------------------------------
+
+“Dropbear†component documentation contains a patent and trademark notice:
+
+ The author (Tom St Denis) is not a patent lawyer so this section is not to
+ be treated as legal advice. To the best of the author’s knowledge, the only
+ patent-related issues within the library are the RC5 and RC6 symmetric block
+ cyphers. They can be removed from a build by simply commenting out the two
+ appropriate lines in `\textit{tomcrypt\_custom.h}`. The rest of the cyphers
+ and hashes are patent-free or under patents that have since expired.
+
+ The RC2 and RC4 symmetric cyphers are not under patents but are under
+ trademark regulations. This means you can use the cyphers you just can’t
+ advertise that you are doing so.
+
+To our best knowledge, also patents on RC5 and RC6 symmetric block cyphers have
+expired, but you should seek legal advice to check whether there still are
+active patents covering such technologies.
+
+.. [*]
+ Carlo Piana and Alberto Pianon from Array (Legal); Rahul Mohan G. and
+ Vaishali Avhad from NOI Techpark (Audit)
+.. [*] SBOM is short for Software Bill Of Material, the full and detailed list
+ of upstream components. SPDX is short for Software Package Data Exchange, an
+ `ISO standard <https://spdx.github.io/spdx-spec>`_ to communicate
+ information about software in a machine-readable form.
+
+.. _toolchain: https://projects.eclipse.org/projects/oniro.oniro-compliancetoolchain
+.. _process: https://gitlab.eclipse.org/eclipse/oniro-compliancetoolchain/toolchain/docs/-/tree/main/audit_workflow
+.. _Fossology: https://www.fossology.org
+.. _Scancode: https://nexb.com/scancode
+.. _official documentation: https://gitlab.eclipse.org/eclipse/oniro-compliancetoolchain/toolchain/docs
+.. _tinfoilhat: https://gitlab.eclipse.org/eclipse/oniro-compliancetoolchain/toolchain/tinfoilhat
+.. _aliens4friends: https://gitlab.eclipse.org/eclipse/oniro-compliancetoolchain/toolchain/aliens4friends
+.. _dashboard: https://gitlab.eclipse.org/eclipse/oniro-compliancetoolchain/toolchain/dashboard
+.. _pipelines: https://gitlab.eclipse.org/eclipse/oniro-compliancetoolchain/toolchain/pipelines
+.. _EULA: https://git.yoctoproject.org/meta-freescale/tree/EULA
+.. _linux-firmware-20220913.tar.xz: https://cdn.kernel.org/pub/linux/kernel/firmware/linux-firmware-20220913.tar.xz
+.. _issue #834: https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/issues/834
+.. _zephyr-philosophers: https://github.com/zephyrproject-rtos/zephyr
+.. _dedicated dashboard: https://sca.software.bz.it/?json=https://gitlab.eclipse.org/eclipse/oniro-compliancetoolchain/mirrors/oniro-goofy/-/jobs/artifacts/kirkstone/raw/report.harvest.json?job=harvest
diff --git a/releases/2.0/2.0.0/release_notes.rst b/releases/2.0/2.0.0/release_notes.rst
new file mode 100644
index 0000000000000000000000000000000000000000..d3b94a7c111132845c499ffee300d1d39f03a7b0
--- /dev/null
+++ b/releases/2.0/2.0.0/release_notes.rst
@@ -0,0 +1,218 @@
+.. SPDX-FileCopyrightText: Huawei Inc.
+..
+.. SPDX-License-Identifier: CC-BY-4.0
+
+.. include:: ../../../definitions.rst
+
+Release Notes
+#############
+
+About
+*****
+
+The objective of this document is to provide basic introductory information
+about included functionalities, known issues and instructions guidance for the
+2.0.0 release of the |main_project_name| project.
+
+The |main_project_name| project serves as a solid base foundation for products.
+It is not a standalone product itself but rather a platform that aims at
+accelerating the development and maintenance of other projects and products.
+
+During this release, the project's code and most of its infrastructure moved to
+Eclipse Foundation as one of the top-level projects. This follows the fact that
+|main_project_name| became an Eclipse Foundation project during a preview
+release iteration.
+
+Scope
+*****
+
+The Objectives of the Release
+-----------------------------
+
+The objective of the *2.0.0* release is to consolidate the features previously
+released, add new outstanding features and meet the requirements defined by the
+Eclipse Foundation Development Process. That includes, but is not limited to:
+
+- Migration of code to Eclipse Foundation
+- Work towards migration of the project's infrastructure to Eclipse Foundation
+ (eg. CI, pipelines, etc.)
+- Hardware & Software roadmap expansion
+- Deployment of the IP compliance toolchain and related policies
+- Security and maintenance featuring CVE fixes, LEDGE support, etc.
+
+The List of Software Features Included
+--------------------------------------
+
+- Linux Kernel LTS version supported for all ARM and X86 targets
+- Zephyr kernel 3.1 supported for all ARM and X86 targets
+- Over-the-Air system update, including integration with hawkbit and SysOTA
+ backends
+- Toolchain package upgrades including LLVM, GCC, musl, etc.
+- Matter 1.0 and Thread 1.2 support
+- Modbus support with RTU (over RS485) and TCP modes
+- New hardware supported: Raspberry Pi 3, SECO (SBC-C61, SBC-B68, SBC-D23),
+ QEMU ARM 32/64bit, Arduino Nano 33 BLE
+- Development and integration of functional testing suites
+- Integration of standard test toolkits (eg. LTP)
+- More LAVA support development including new LAVA nodes
+- Security OS features targeting runtime and build-time (:ref:`SecurityGuide`)
+- Development for security-oriented features for Oniro upgrades and CVE fixes
+- Upstream contributions in terms of fixes, backports and CVE issues
+- Repackaging of |main_project_name| from monolithic to modular, leveraging the
+ Yocto Project layer architecture, as well as the Eclipse Foundation
+ sub-project structure
+- Split Blueprints, Sysota, and OpenHarmony components into their sub-project
+
+For more details, a full list of requiremnts can be seen
+:ref:`here<2_0_0_Requirements>`.
+
+Supported Hardware Platforms
+----------------------------
+
++---------------------------------+-------------------+---------------------------------------+
+| Board (chipset) | Supported kernels | Board documentation |
++=================================+===================+=======================================+
+| QEMU X86 | Linux & Zephyr | :ref:`SupportedVBoardQemuX86` |
++---------------------------------+-------------------+---------------------------------------+
+| QEMU X86-64 | Linux | :ref:`SupportedVBoardQemuX86-64` |
++---------------------------------+-------------------+---------------------------------------+
+| QEMU ARM (EFI) | Linux | :ref:`SupportedVBoardQemuARM` |
++---------------------------------+-------------------+---------------------------------------+
+| QEMU ARM64 (EFI) | Linux | :ref:`SupportedVBoardQemuARM64` |
++---------------------------------+-------------------+---------------------------------------+
+| QEMU Cortex M3 | Zephyr | :ref:`Zephyr_Kernel` |
++---------------------------------+-------------------+---------------------------------------+
+| SECO SBC-B68 | Linux | :ref:`SupportedBoardSecoB68` |
++---------------------------------+-------------------+---------------------------------------+
+| SECO SBC-C61 | Linux | :ref:`SupportedBoardSecoC61` |
++---------------------------------+-------------------+---------------------------------------+
+| SECO SBC-D23 | Linux | :ref:`SupportedBoardSecoD23` |
++---------------------------------+-------------------+---------------------------------------+
+| Raspberry Pi 4 B (BCM2711) | Linux | :ref:`raspberrypi` |
++---------------------------------+-------------------+---------------------------------------+
+| Raspberry Pi 3 B+ (BCM2837B0) | Linux | :ref:`raspberrypi` |
++---------------------------------+-------------------+---------------------------------------+
+| Arduino Nano 33 BLE | Zephyr | :ref:`SupportedBoardArduinoNano33BLE` |
++---------------------------------+-------------------+---------------------------------------+
+
+Installation
+************
+
+:ref:`Quick Build <OniroQuickBuild>` provides an example of how to build the
+|main_project_name| project for an example 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 instructions how
+to prepare the workspace for development. Since |main_project_name| uses `repo`
+tool for its development, you can use the release tag for the `repo init`
+commands as follows:
+
+.. code-block:: console
+
+ repo init -u https://gitlab.eclipse.org/eclipse/oniro-core/oniro.git -b v2.0.0
+
+Known Issues
+------------
+
+Visit `this link
+<https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/issues/?sort=label_priority_desc&state=all&label_name%5B%5D=KnownIssue%3A%3ARelease2.0.0&first_page_size=20>`__
+to see known issues for this release.
+
+Source Code
+-----------
+
+For more details on our repo structure, see `OniroProject's GitLab
+<https://gitlab.eclipse.org/eclipse/oniro-core>`__ project group.
+
+DevOps Infrastructure
+*********************
+
+To learn more about our approach to CI (Continuous Integration) strategy used
+for this release, please see:
+
+:doc:`/ci/index` document.
+
+Testing
+-------
+
+Details can be found in:
+
+:doc:`/ci/device-testing` document.
+
+This release comes with a detailed `Test Report` accesible
+:ref:`here<2_0_0_TestReport>`.
+
+IP Compliance
+-------------
+
+This release comes with a detailed `IP Compliance note` accesible
+:ref:`here<2_0_0_IPComplianceNote>`.
+
+Security Status
+---------------
+
+This release comes with a detailed `Security report` with a list of known CVEs
+accessible :ref:`here<2_0_0_SecurityReport>`.
+
+As part of the Oniro continuous compliance process, all relevant metadata about
+compliance and security are collected at build time for every commit to the
+Oniro project repo, and can be inspected through a `dedicated dashboard`_. Open
+CVEs on single components data may be inspected by filtering components by
+status ("has unpatched CVEs") and by opening the component details: open CVEs
+are displayed first, marked in red and ordered by score, while closed CVEs are
+marked in green. The dashboard gets updated after every commit and contains a
+CVE status snapshot at the time of the commit. However, if some previously open
+CVEs are fixed, this would be visible by inspecting the component's previous
+variants in the dashboard.
+
+.. _dedicated dashboard: https://sca.software.bz.it/?json=https://gitlab.eclipse.org/eclipse/oniro-compliancetoolchain/mirrors/oniro-goofy/-/jobs/artifacts/kirkstone/raw/report.harvest.json?job=harvest
+
+Out of Scope
+************
+
+|main_project_name| bundles components from multiple upstream sources. These
+upstream sources come with features that the project might not explicitly
+mention as part of its supportability policy. Similarly, |main_project_name|
+includes supported features that are explicitly marked as 'experimental'. All
+these cases, mainly driven by the community, will imply basic support from the
+project.
+
+|main_project_name| exercises an upstream-first support policy, so even for
+cases that are not strictly in the supportability scope of the project,
+|main_project_name| will provide guidance and traceability while facilitating
+the upstream effort.
+
+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 in our
+|main_project_name| ecosystem development. To do so, please sign-up using the
+process described below:
+
+:doc:`/contributing/index` document.
+
+License
+*******
+
+Project manifest, project-specific meta-layers, recipes, and software packages
+are published under the MIT license unless specified otherwise. 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 license conditions.
+
+Official project release includes only the project manifest, project-specific
+meta-layers, and recipes. Any reference binary image, build cache, and other
+build artefacts are distributed only as a convenience and are not part of the
+release itself.
+
+.. note::
+
+ "supported" `referred to a board` means that a board is officially targeted
+ as a potential platform where an Oniro image can be installed for any
+ purposes; when `referred to an image`, means that the image targeting a
+ supported board receives thorough testing and specific attention during the
+ development. It does NOT mean that both will receive support services nor
+ that any member of the Oniro Working Group or of the Eclipse Foundation will
+ provide any warranty whatsoever.
diff --git a/releases/2.0/2.0.0/requirements.rst b/releases/2.0/2.0.0/requirements.rst
new file mode 100644
index 0000000000000000000000000000000000000000..fb586fa5dc36d6a26b964c05af2c09b8d994a925
--- /dev/null
+++ b/releases/2.0/2.0.0/requirements.rst
@@ -0,0 +1,117 @@
+.. SPDX-FileCopyrightText: Huawei Inc.
+..
+.. SPDX-License-Identifier: CC-BY-4.0
+
+.. include:: ../../../definitions.rst
+
+.. _2_0_0_Requirements:
+
+Release Requirements
+####################
+
+The development process in |main_project_name| is based on requirements. They
+represent in a written form, the aims of a release that satisfy them. The
+`2.0.0` release, includes the following requirements that were addressed during
+its development cycle:
+
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|Domain |Feature/deliverable |Gitlab Epics/Issues |
++======================+==========================================================+=======================================================================================================================================================================+
+|Kernels |Linux 5.1x LTS |`Linux kernel LTS version for ARM and X86 targets <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/58>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Zephyr LTS |`Zephyr kernel version 3.1 for X86 and ARM targets <https://gitlab.eclipse.org/groups/ec¨lipse/oniro-core/-/epics/10>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|OTA |System OTA Linux |`System OTA - Linux target <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/18>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |System OTA end-to-end including cloud backend |`OTA Cloud Backend Integration <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/10>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|Toolchains |Toolchain LTS |`Toolchain LTS version <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/1>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |LLVM |`Toolchain LLVM Integration <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/85>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |GCC |`Toolchain GCC Integration <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/84>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`Toolchain GCC CI Integration <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/86>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|Networking |RS485, Modbus RTU and TCP |`RS485, Modbus RTU and TCP support <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/11>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |OpenThread 1.2 |`OpenThread update to support Thread 1.2 <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/6>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Matter for Linux |`Matter network protocol support for Linux <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/5>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`Research and Document the Project Matter specification version Goofy will be compatible with <https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/issues/445>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|Reference Hardware |Seco SBC C61 - NXP i.MX8M Mini - Linux |`SECO ASTRID (SBC-C61) - Linux <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/34>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Seco SBC B68 - Intel Atom - Linux |`SECO ALVIN - SBC-B68 - Linux <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/35>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Seco D23 - Rockchip - Linux and Zephyr |`SECO JUNO (SBC-D23) - Linux <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/38>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Arduino Nano BLE - Zephyr |`Arduino Nano BLE - Zephyr <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/32>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |RPi 3/4 - Linux |`Raspberry Pi 3/4 - Linux <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/33>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |QEMU for Intel, ARM - Linux, Zephyr |`QEMU targets <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/41>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|Infrastructure |Eclipse Foundation migration |`Eclipse Foundation migration <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/139>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|Testing |Completion of LAVA testing infrastructure |`Complete LAVA testing infrastructure <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/14>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Additional lab online - NOI Techpark |`Setup an Oniro HW LAVA lab at NOI Techpark <https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/issues/253>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`Enable functional verification Oniro HW LAVA lab at NOI Techpark <https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/issues/254>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Additional lab online - Kalpa |`LAVA node setup in Kalpa <https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/issues/592>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |More DUTs - Warsaw lab |`Add one more RPi4 to the WRC lab <https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/issues/569>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`Add one more C61 to the WRC lab <https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/issues/646>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Periodic report of functional and performance verification|`Periodic reporting of results of functional testing and performance benchmarking <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/15>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Integration of standard test toolkits |`Add LTP test plan across the board <https://git.ostc-eu.org/OSTC/infrastructure/infrastructure-maintenence/-/issues/30>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Integration of functional test suites |`Integration of functional test suites into Oniro CI <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/46>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|Documentation & UX |Tests of all reference platforms code after migration |`UX: Test the code on all reference platforms after migrate repos to Eclipse Foundation <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/133>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Tests of blueprints code building |`UX: Blueprints Code Build I Retest [booting.oniro.org] <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/137>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+|Security & Maintenance|Secure-by-default Linux images |`Debug/production builds <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/140>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`User and login hardening <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/130>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`Security processes for Goofy <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/111>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`Document security hardening options and decisions <https://gitlab.eclipse.org/eclipse/oniro-core/docs/-/issues/14>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Security, Vulnerability, Bugfix management tools |`Yocto SBOM generation tool in Oniro <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/101>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`JSON-based output of cve-check <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/98>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`Integrate bugfix and security data into the IP toolchain dashboard <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/121>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`Oniro upgrade delta check tool <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/100>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |LEDGE RP Compatibility for Oniro |`Use meta-ledge in Oniro <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/112>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`Use meta-ts in Oniro <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/113>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`Research and Document the target LEDGE Release for Goofy inclusion <https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/issues/446>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |CVE Fixes |`CVE fixes March 2022 <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/138>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`June CVE fixes <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/146>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`July CVE fixes <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/150>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`August CVE fixes <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/155>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| |Upstream security issues backports |`Kirkstone backports for April 2022 <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/141>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`Kirkstone backports for May 2022 <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/142>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`June backports to kirkstone <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/144>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+| | |`August backports to kirkstone <https://gitlab.eclipse.org/groups/eclipse/oniro-core/-/epics/154>`_ |
++----------------------+----------------------------------------------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------+
diff --git a/releases/2.0/2.0.0/security_report.rst b/releases/2.0/2.0.0/security_report.rst
new file mode 100644
index 0000000000000000000000000000000000000000..4250e7b023cc8c4df986350d3a8e083152e119a7
--- /dev/null
+++ b/releases/2.0/2.0.0/security_report.rst
@@ -0,0 +1,224 @@
+.. SPDX-FileCopyrightText: Linaro Ltd
+
+.. SPDX-License-Identifier: CC-BY-4.0
+
+.. _2_0_0_SecurityReport:
+
+Security Test Report (as of Nov 25, 2022)
+=========================================
+
+The CVEs have been checked against the NVD database as of Nov 25th, 2022.
+
+qemu x86-64 CVE report (root filesystem only)
+---------------------------------------------
+
+Total number of known issues: 378
+
+Out of this, high severity (CVSSv3 >= 7.0): 122
+
+Complete results:
+
+.. code-block:: console
+
+ Issues for package curl (version 7.82.0):
+ CVE-2022-42915 CVE-2022-42916
+ Count: 2
+
+ Issues for package expat (version 2.4.9):
+ CVE-2022-43680
+ Count: 1
+
+ Issues for package podman (version 4.0.1+gitAUTOINC+717edd7b84):
+ CVE-2022-2989
+ Count: 1
+
+ Issues for package dropbear (version 2020.81):
+ CVE-2021-36369
+ Count: 1
+
+ Issues for package openssl (version 3.0.5):
+ CVE-2022-3358 CVE-2022-3602 CVE-2022-3786
+ Count: 3
+
+ Issues for package systemd (version 1_250.5):
+ CVE-2022-3821
+ Count: 1
+
+ Issues for package linux-oniro (version 5.10.152+gitAUTOINC+dd90d836c0_b2303e799c):
+ CVE-1999-0524 CVE-1999-0656 CVE-2006-2932 CVE-2007-2764 CVE-2007-4998 CVE-2008-2544
+ CVE-2008-4609 CVE-2010-0298 CVE-2010-4563 CVE-2014-2648 CVE-2014-8171 CVE-2016-0774
+ CVE-2016-3695 CVE-2016-3699 CVE-2017-1000255 CVE-2017-1000377 CVE-2017-6264
+ CVE-2018-1000026 CVE-2018-10840 CVE-2018-10876 CVE-2018-10882 CVE-2018-10901 CVE-2018-10902
+ CVE-2018-14625 CVE-2018-16880 CVE-2018-16884 CVE-2018-5873 CVE-2018-6559 CVE-2019-14899
+ CVE-2019-18910 CVE-2019-3016 CVE-2019-3819 CVE-2019-3846 CVE-2019-3887 CVE-2020-10732
+ CVE-2020-10742 CVE-2020-16119 CVE-2020-16120 CVE-2020-1749 CVE-2020-25639 CVE-2020-25672
+ CVE-2020-26558 CVE-2020-27170 CVE-2020-27171 CVE-2020-27784 CVE-2020-27820 CVE-2020-35499
+ CVE-2020-35501 CVE-2020-35508 CVE-2020-8834 CVE-2021-20194 CVE-2021-20226 CVE-2021-20265
+ CVE-2021-20320 CVE-2021-20321 CVE-2021-20322 CVE-2021-23133 CVE-2021-23134 CVE-2021-27363
+ CVE-2021-27364 CVE-2021-27365 CVE-2021-28038 CVE-2021-28039 CVE-2021-28375 CVE-2021-28660
+ CVE-2021-28691 CVE-2021-28714 CVE-2021-28715 CVE-2021-28950 CVE-2021-28951 CVE-2021-28952
+ CVE-2021-28964 CVE-2021-28971 CVE-2021-28972 CVE-2021-29154 CVE-2021-29155 CVE-2021-29264
+ CVE-2021-29265 CVE-2021-29266 CVE-2021-29646 CVE-2021-29647 CVE-2021-29648 CVE-2021-29649
+ CVE-2021-29650 CVE-2021-29657 CVE-2021-30002 CVE-2021-30178 CVE-2021-31829 CVE-2021-31916
+ CVE-2021-32078 CVE-2021-32399 CVE-2021-33033 CVE-2021-33034 CVE-2021-33200 CVE-2021-33624
+ CVE-2021-33655 CVE-2021-33909 CVE-2021-34556 CVE-2021-34693 CVE-2021-3483 CVE-2021-3501
+ CVE-2021-35039 CVE-2021-3506 CVE-2021-35477 CVE-2021-3564 CVE-2021-3573 CVE-2021-3609
+ CVE-2021-3640 CVE-2021-3653 CVE-2021-3655 CVE-2021-3656 CVE-2021-3659 CVE-2021-3669
+ CVE-2021-3679 CVE-2021-3714 CVE-2021-37159 CVE-2021-3732 CVE-2021-3736 CVE-2021-3739
+ CVE-2021-3744 CVE-2021-3752 CVE-2021-3753 CVE-2021-37576 CVE-2021-3759 CVE-2021-3764
+ CVE-2021-3772 CVE-2021-3773 CVE-2021-38160 CVE-2021-38166 CVE-2021-38198 CVE-2021-38199
+ CVE-2021-38200 CVE-2021-38201 CVE-2021-38202 CVE-2021-38203 CVE-2021-38204 CVE-2021-38205
+ CVE-2021-38206 CVE-2021-38207 CVE-2021-38208 CVE-2021-38209 CVE-2021-38300 CVE-2021-3847
+ CVE-2021-3864 CVE-2021-4001 CVE-2021-4002 CVE-2021-4023 CVE-2021-4032 CVE-2021-4037
+ CVE-2021-40490 CVE-2021-4083 CVE-2021-4090 CVE-2021-4093 CVE-2021-4095 CVE-2021-41073
+ CVE-2021-4135 CVE-2021-4148 CVE-2021-4149 CVE-2021-4150 CVE-2021-4154 CVE-2021-4155
+ CVE-2021-4157 CVE-2021-41864 CVE-2021-4197 CVE-2021-42008 CVE-2021-4202 CVE-2021-4203
+ CVE-2021-4218 CVE-2021-42252 CVE-2021-42327 CVE-2021-42739 CVE-2021-43057 CVE-2021-43389
+ CVE-2021-43975 CVE-2021-43976 CVE-2021-44733 CVE-2021-44879 CVE-2021-45095 CVE-2021-45402
+ CVE-2021-45469 CVE-2021-45480 CVE-2021-45485 CVE-2021-45486 CVE-2021-45868 CVE-2021-46283
+ CVE-2022-0168 CVE-2022-0171 CVE-2022-0185 CVE-2022-0264 CVE-2022-0286 CVE-2022-0322
+ CVE-2022-0330 CVE-2022-0382 CVE-2022-0400 CVE-2022-0433 CVE-2022-0435 CVE-2022-0480
+ CVE-2022-0487 CVE-2022-0492 CVE-2022-0494 CVE-2022-0500 CVE-2022-0516 CVE-2022-0617
+ CVE-2022-0850 CVE-2022-0854 CVE-2022-0995 CVE-2022-0998 CVE-2022-1011 CVE-2022-1012
+ CVE-2022-1015 CVE-2022-1016 CVE-2022-1043 CVE-2022-1048 CVE-2022-1055 CVE-2022-1158
+ CVE-2022-1184 CVE-2022-1195 CVE-2022-1198 CVE-2022-1199 CVE-2022-1204 CVE-2022-1205
+ CVE-2022-1247 CVE-2022-1263 CVE-2022-1353 CVE-2022-1462 CVE-2022-1508 CVE-2022-1651
+ CVE-2022-1652 CVE-2022-1671 CVE-2022-1734 CVE-2022-1786 CVE-2022-1852 CVE-2022-1882
+ CVE-2022-1973 CVE-2022-1976 CVE-2022-1998 CVE-2022-2078 CVE-2022-2153 CVE-2022-2308
+ CVE-2022-2318 CVE-2022-23222 CVE-2022-2327 CVE-2022-2380 CVE-2022-24448 CVE-2022-24958
+ CVE-2022-24959 CVE-2022-2503 CVE-2022-25258 CVE-2022-25265 CVE-2022-25375 CVE-2022-26365
+ CVE-2022-26490 CVE-2022-2663 CVE-2022-26878 CVE-2022-26966 CVE-2022-27223 CVE-2022-27666
+ CVE-2022-2785 CVE-2022-27950 CVE-2022-28356 CVE-2022-28388 CVE-2022-28389 CVE-2022-28390
+ CVE-2022-2873 CVE-2022-28796 CVE-2022-28893 CVE-2022-2905 CVE-2022-29156 CVE-2022-2938
+ CVE-2022-29581 CVE-2022-29582 CVE-2022-2959 CVE-2022-2961 CVE-2022-2977 CVE-2022-2991
+ CVE-2022-29968 CVE-2022-3028 CVE-2022-3077 CVE-2022-3078 CVE-2022-3170 CVE-2022-3176
+ CVE-2022-3202 CVE-2022-32250 CVE-2022-32296 CVE-2022-32981 CVE-2022-3303 CVE-2022-3344
+ CVE-2022-33740 CVE-2022-33741 CVE-2022-33742 CVE-2022-33743 CVE-2022-33744 CVE-2022-33981
+ CVE-2022-3435 CVE-2022-34494 CVE-2022-34495 CVE-2022-34918 CVE-2022-3521 CVE-2022-3522
+ CVE-2022-3523 CVE-2022-3526 CVE-2022-3531 CVE-2022-3532 CVE-2022-3533 CVE-2022-3534
+ CVE-2022-3535 CVE-2022-3541 CVE-2022-3542 CVE-2022-3543 CVE-2022-3544 CVE-2022-3545
+ CVE-2022-3563 CVE-2022-3564 CVE-2022-3565 CVE-2022-3566 CVE-2022-3567 CVE-2022-3586
+ CVE-2022-3594 CVE-2022-3595 CVE-2022-3606 CVE-2022-36123 CVE-2022-3619 CVE-2022-3621
+ CVE-2022-3623 CVE-2022-3624 CVE-2022-3625 CVE-2022-36280 CVE-2022-3629 CVE-2022-3630
+ CVE-2022-3633 CVE-2022-3635 CVE-2022-3636 CVE-2022-3637 CVE-2022-3640 CVE-2022-36402
+ CVE-2022-3646 CVE-2022-3649 CVE-2022-36879 CVE-2022-36946 CVE-2022-38096 CVE-2022-38457
+ CVE-2022-39188 CVE-2022-39189 CVE-2022-39190 CVE-2022-39842 CVE-2022-40133 CVE-2022-40307
+ CVE-2022-40476 CVE-2022-40768 CVE-2022-41218 CVE-2022-41222 CVE-2022-41674 CVE-2022-41848
+ CVE-2022-41849 CVE-2022-41850 CVE-2022-42703 CVE-2022-42719 CVE-2022-42720 CVE-2022-42721
+ CVE-2022-42722 CVE-2022-43750 CVE-2022-43945 CVE-2022-44032 CVE-2022-44033 CVE-2022-44034
+ Count: 365
+
+ Issues for package sudo (version 1.9.10):
+ CVE-2022-43995
+ Count: 1
+
+ Issues for package python3 (version 3.10.7):
+ CVE-2022-42919 CVE-2022-45061
+ Count: 2
+
+ Issues for package libpam (version 1.5.2):
+ CVE-2022-28321
+ Count: 1
+
+raspberrypi4 CVE report (rootfs only)
+-------------------------------------
+
+Total number of known issues: 249
+
+Out of this, high severity (CVSSv3 >= 7.0): 118
+
+Complete results:
+
+.. code-block:: console
+
+ Issues for package systemd (version 1_250.5):
+ CVE-2022-3821
+ Count: 1
+
+ Issues for package openssl (version 3.0.5):
+ CVE-2022-3358 CVE-2022-3602 CVE-2022-3786
+ Count: 3
+
+ Issues for package libpam (version 1.5.2):
+ CVE-2022-28321
+ Count: 1
+
+ Issues for package linux-raspberrypi (version1_5.15.34+gitAUTOINC+e1b976ee4f_0086da6acd):
+ CVE-1999-0524 CVE-1999-0656 CVE-2006-2932 CVE-2007-2764
+ CVE-2007-4998 CVE-2008-2544 CVE-2008-4609 CVE-2010-0298 CVE-2010-4563
+ CVE-2014-2648 CVE-2014-8171 CVE-2016-0774 CVE-2016-3695 CVE-2016-3699
+ CVE-2017-1000255 CVE-2017-1000377 CVE-2017-6264 CVE-2018-1000026
+ CVE-2018-10840 CVE-2018-10876 CVE-2018-10882 CVE-2018-10901
+ CVE-2018-10902 CVE-2018-14625 CVE-2018-16880 CVE-2018-16884
+ CVE-2018-5873 CVE-2018-6559 CVE-2019-14899 CVE-2019-18910
+ CVE-2019-3016 CVE-2019-3819 CVE-2019-3846 CVE-2019-3887 CVE-2020-10732
+ CVE-2020-10742 CVE-2020-16119 CVE-2020-1749 CVE-2020-25672
+ CVE-2020-27784 CVE-2020-27820 CVE-2020-35501 CVE-2020-8834
+ CVE-2021-20194 CVE-2021-20226 CVE-2021-20265 CVE-2021-33655
+ CVE-2021-3564 CVE-2021-3669 CVE-2021-3714 CVE-2021-3743 CVE-2021-3759
+ CVE-2021-3847 CVE-2021-3864 CVE-2021-4002 CVE-2021-4090 CVE-2021-4095
+ CVE-2021-4135 CVE-2021-4155 CVE-2021-4197 CVE-2021-4202 CVE-2021-4218
+ CVE-2021-44879 CVE-2021-45402 CVE-2022-0168 CVE-2022-0171
+ CVE-2022-0185 CVE-2022-0264 CVE-2022-0286 CVE-2022-0330 CVE-2022-0382
+ CVE-2022-0400 CVE-2022-0433 CVE-2022-0435 CVE-2022-0480 CVE-2022-0492
+ CVE-2022-0494 CVE-2022-0500 CVE-2022-0516 CVE-2022-0617 CVE-2022-0742
+ CVE-2022-0854 CVE-2022-0995 CVE-2022-0998 CVE-2022-1011 CVE-2022-1012
+ CVE-2022-1015 CVE-2022-1016 CVE-2022-1048 CVE-2022-1055 CVE-2022-1158
+ CVE-2022-1184 CVE-2022-1195 CVE-2022-1198 CVE-2022-1199 CVE-2022-1204
+ CVE-2022-1205 CVE-2022-1247 CVE-2022-1263 CVE-2022-1353 CVE-2022-1462
+ CVE-2022-1651 CVE-2022-1652 CVE-2022-1671 CVE-2022-1734 CVE-2022-1852
+ CVE-2022-1882 CVE-2022-1973 CVE-2022-1976 CVE-2022-1998 CVE-2022-2078
+ CVE-2022-2153 CVE-2022-2308 CVE-2022-2318 CVE-2022-2327 CVE-2022-2380
+ CVE-2022-24122 CVE-2022-24448 CVE-2022-24958 CVE-2022-24959
+ CVE-2022-2503 CVE-2022-25258 CVE-2022-25265 CVE-2022-25375
+ CVE-2022-26365 CVE-2022-26490 CVE-2022-2663 CVE-2022-26878
+ CVE-2022-26966 CVE-2022-27223 CVE-2022-27666 CVE-2022-2785
+ CVE-2022-27950 CVE-2022-28356 CVE-2022-28388 CVE-2022-28389
+ CVE-2022-28390 CVE-2022-2873 CVE-2022-28796 CVE-2022-28893
+ CVE-2022-2905 CVE-2022-29156 CVE-2022-2938 CVE-2022-29581
+ CVE-2022-29582 CVE-2022-2959 CVE-2022-2961 CVE-2022-2977
+ CVE-2022-29968 CVE-2022-3028 CVE-2022-3077 CVE-2022-3078 CVE-2022-3170
+ CVE-2022-3176 CVE-2022-3202 CVE-2022-32250 CVE-2022-32296
+ CVE-2022-32981 CVE-2022-3303 CVE-2022-3344 CVE-2022-33740
+ CVE-2022-33741 CVE-2022-33742 CVE-2022-33743 CVE-2022-33744
+ CVE-2022-33981 CVE-2022-3435 CVE-2022-34494 CVE-2022-34495
+ CVE-2022-34918 CVE-2022-3521 CVE-2022-3522 CVE-2022-3523 CVE-2022-3526
+ CVE-2022-3531 CVE-2022-3532 CVE-2022-3533 CVE-2022-3534 CVE-2022-3535
+ CVE-2022-3541 CVE-2022-3542 CVE-2022-3543 CVE-2022-3544 CVE-2022-3545
+ CVE-2022-3563 CVE-2022-3564 CVE-2022-3565 CVE-2022-3566 CVE-2022-3567
+ CVE-2022-3586 CVE-2022-3594 CVE-2022-3595 CVE-2022-3606 CVE-2022-36123
+ CVE-2022-3619 CVE-2022-3621 CVE-2022-3623 CVE-2022-3624 CVE-2022-3625
+ CVE-2022-3629 CVE-2022-3630 CVE-2022-3633 CVE-2022-3635 CVE-2022-3636
+ CVE-2022-3637 CVE-2022-3640 CVE-2022-36402 CVE-2022-3646 CVE-2022-3649
+ CVE-2022-36879 CVE-2022-36946 CVE-2022-38096 CVE-2022-38457
+ CVE-2022-39188 CVE-2022-39189 CVE-2022-39190 CVE-2022-39842
+ CVE-2022-40133 CVE-2022-40307 CVE-2022-40476 CVE-2022-40768
+ CVE-2022-41218 CVE-2022-41674 CVE-2022-41848 CVE-2022-41849
+ CVE-2022-41850 CVE-2022-42703 CVE-2022-42719 CVE-2022-42720
+ CVE-2022-42721 CVE-2022-42722 CVE-2022-43750 CVE-2022-43945
+ CVE-2022-44032 CVE-2022-44033 CVE-2022-44034
+ Count: 236
+
+ Issues for package curl (version 7.82.0):
+ CVE-2022-42915 CVE-2022-42916
+ Count: 2
+
+ Issues for package python3 (version 3.10.7):
+ CVE-2022-42919 CVE-2022-45061
+ Count: 2
+
+ Issues for package expat (version 2.4.9):
+ CVE-2022-43680
+ Count: 1
+
+ Issues for package dropbear (version 2020.81):
+ CVE-2021-36369
+ Count: 1
+
+ Issues for package sudo (version 1.9.10):
+ CVE-2022-43995
+ Count: 1
+
+ Issues for package podman (version 4.0.1+gitAUTOINC+717edd7b84):
+ CVE-2022-2989
+ Count: 1
diff --git a/releases/2.0/2.0.0/test_report.rst b/releases/2.0/2.0.0/test_report.rst
new file mode 100644
index 0000000000000000000000000000000000000000..9eae36531cecbc469f2ad2e70f698f42f0c82f88
--- /dev/null
+++ b/releases/2.0/2.0.0/test_report.rst
@@ -0,0 +1,64 @@
+.. SPDX-FileCopyrightText: Luca Favaretto <luca.favaretto@kalpa.it> and Luca zizolfi <luca.zizolfi@kalpa.it>
+..
+.. SPDX-License-Identifier: CC-BY-4.0
+
+.. _2_0_0_TestReport:
+
+Test Report
+==================
+
+Results by test suite
+-----------------------
+
++---------------------+-------------------+-------+---------+---------+---------+----------+------+-----------+
+| TESTS | Manual Automated | TEST | NO RUN | PASSED | FAILED | BLOCKED | N/A | SKIPPED |
++=====================+===================+=======+=========+=========+=========+==========+======+===========+
+| Kernel Build | Both | 32 | 0 | 24 | 6 | | 2 | |
++---------------------+-------------------+-------+---------+---------+---------+----------+------+-----------+
+| OTA | Automated | 6 | 0 | 6 | | | | |
++---------------------+-------------------+-------+---------+---------+---------+----------+------+-----------+
+| Networking | Manual | 2 | 0 | | | 1 | | 1 |
++---------------------+-------------------+-------+---------+---------+---------+----------+------+-----------+
+| Reference Hardware | Manual | 48 | 0 | 10 | | 29 | 5 | 4 |
++---------------------+-------------------+-------+---------+---------+---------+----------+------+-----------+
+| Security | Manual | 170 | 0 | 157 | | | 13 | |
++---------------------+-------------------+-------+---------+---------+---------+----------+------+-----------+
+| Podman | Automated | 1300 | 0 | 234 | 960 | | 106 | |
++---------------------+-------------------+-------+---------+---------+---------+----------+------+-----------+
+| LTP | Automated | 15030 | 0 | 12381 | 520 | | 2129 | |
++---------------------+-------------------+-------+---------+---------+---------+----------+------+-----------+
+| Kernel self test | Automated | 56 | 0 | 8 | 24 | | 24 | |
++---------------------+-------------------+-------+---------+---------+---------+----------+------+-----------+
+| Libc | Automated | 2185 | 0 | 1464 | 721 | | | |
++---------------------+-------------------+-------+---------+---------+---------+----------+------+-----------+
+
+Overall Results
+-----------------
+
++--------------------+------------+
+| **Total** | **23442** |
++--------------------+------------+
+| | |
++--------------------+------------+
+| *Passed* | *17994* |
++--------------------+------------+
+| *Failed* | *2324* |
++--------------------+------------+
+| *Blocked* | *30* |
++--------------------+------------+
+| *Skipped* | *5* |
++--------------------+------------+
+| *Out of scope* | *3089* |
++--------------------+------------+
+| *No Run* | *0* |
++--------------------+------------+
+| | |
++--------------------+------------+
+| **TEST PASS RATE** | **89,94%** |
++--------------------+------------+
+| % Blocked | 0,13% |
++--------------------+------------+
+| % Failed | 9,91% |
++--------------------+------------+
+| % Skipped | 0,02% |
++--------------------+------------+
diff --git a/releases/index.rst b/releases/index.rst
index 986aab9bb27fd70f43620c3173c45d65d04edb08..8b0041a0aa6c7205505ac0d5a9e1582f86e4a7de 100644
--- a/releases/index.rst
+++ b/releases/index.rst
@@ -14,3 +14,4 @@ This section contains information related to releases of |main_project_name|.
aladeen/0.1.0/release_notes
jasmine/1.0.0/release_notes
+ 2.0/2.0.0/index
diff --git a/security/guide.rst b/security/guide.rst
index c9a75016658b9bb9009701b0872fae27320a39d7..f93af853a1cff671ea01bf00463cc8036861a3b8 100644
--- a/security/guide.rst
+++ b/security/guide.rst
@@ -4,6 +4,8 @@
.. include:: ../definitions.rst
+.. _SecurityGuide:
+
Security Practices
##################