diff --git a/content/_index.md b/content/_index.md
index 75802cb0dd45486e7341b4561a2105ab2e1fadfe..7fe0e87b8e3991f925b159b902a81e8dda269409 100644
--- a/content/_index.md
+++ b/content/_index.md
@@ -89,7 +89,7 @@ year.
* [Release Schedule]( {{< ref "releases.md" >}} )
* Current stable release: [v2022.3]( {{< ref "/release/v2022.3/releasenotes.md" >}} )
* Current old stable release: [v2021.7]( {{< ref "/release/v2021.7/releasenotes.md" >}} )
-* Current development release: [v2023dev3]( {{< ref "/release/v2023dev3/releasenotes.md" >}} )
+* Current preview release: [v2023pre]( {{< ref "/release/v2023pre/releasenotes.md" >}} )
{{% /link-box %}}
{{% /homepage-column %}}
diff --git a/content/policies/releases.md b/content/policies/releases.md
index 98265dca2fb7c2f4726a8635a49b8659d8967db6..d2d9f05513a741f95ff219266bbd2cb65a286b27 100644
--- a/content/policies/releases.md
+++ b/content/policies/releases.md
@@ -52,17 +52,18 @@ and getting the support of two or more Apertis maintainers.
The latest releases are:
- - v2023dev3: [release notes]( {{< ref "/release/v2023dev3/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2023dev3/release_schedule.md" >}} )
+ - v2023pre: [release notes]( {{< ref "/release/v2023pre/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2023pre/release_schedule.md" >}} )
- v2022.3: [release notes]( {{< ref "/release/v2022.3/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2022.3/release_schedule.md" >}} )
- v2021.7: [release notes]( {{< ref "/release/v2021.7/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2021.7/release_schedule.md" >}} )
The next releases will be:
- v2024dev0: [release schedule]( {{< ref "/release/v2024dev0/release_schedule.md" >}} )
- - v2023pre: [release schedule]( {{< ref "/release/v2023pre/release_schedule.md" >}} )
+ - v2023.0: [release schedule]( {{< ref "/release/v2023.0/release_schedule.md" >}} )
- v2022.4: [release schedule]( {{< ref "/release/v2022.4/release_schedule.md" >}} )
For previous releases see:
+ - v2023dev3: [release notes]( {{< ref "/release/v2023dev3/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2023dev3/release_schedule.md" >}} )
- v2022.2: [release notes]( {{< ref "/release/v2022.2/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2022.2/release_schedule.md" >}} )
- v2021.6: [release notes]( {{< ref "/release/v2021.6/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2021.6/release_schedule.md" >}} )
- v2023dev2: [release notes]( {{< ref "/release/v2023dev2/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2023dev2/release_schedule.md" >}} )
diff --git a/content/release/v2023.0.md b/content/release/v2023.0.md
new file mode 100644
index 0000000000000000000000000000000000000000..8550371fb336d526012ed01da489c9e8be7fa8c6
--- /dev/null
+++ b/content/release/v2023.0.md
@@ -0,0 +1,8 @@
++++
+weight = 100
+title = "v2023.0"
++++
+
+# Release v2023.0
+
+- {{< page-title-ref "/release/v2023.0/release_schedule.md" >}}
\ No newline at end of file
diff --git a/content/release/v2023.0/release_schedule.md b/content/release/v2023.0/release_schedule.md
new file mode 100644
index 0000000000000000000000000000000000000000..4e80ab06094a9fade4fafb03c14852de8eedf5b0
--- /dev/null
+++ b/content/release/v2023.0/release_schedule.md
@@ -0,0 +1,27 @@
++++
+date = "2022-12-07"
+weight = 100
+
+title = "v2023.0 Release schedule"
++++
+
+The v2023.0 release cycle is scheduled to start in January 2023.
+
+| Milestone | Date |
+| -------------------------------------------------------------------------------------------------------- | ----------------- |
+| Start of release cycle | 2023-01-01 |
+| Soft feature freeze: end of feature proposal and review period | 2023-02-08 |
+| Soft code freeze/hard feature freeze: end of feature development for this release, only bugfixes allowed | 2023-02-15 |
+| Release candidate 1 (RC1)/hard code freeze: no new code changes may be made after this date | 2023-02-22 |
+| RC testing | 2023-02-23..03-08 |
+| v2023.0 release | 2023-03-09 |
+
+If the release candidate 1 does not successfully pass all required
+tests, then the issues will be fixed and a new release candidate will be
+re-tested. This would delay the release, which would be reflected on
+this page.
+
+## See also
+
+ - Previous [release schedules]( {{< ref "/policies/releases.md" >}} ) and
+ more information about the timeline
diff --git a/content/release/v2023pre.md b/content/release/v2023pre.md
index cbbf0a981b1b0f3462653ec9c6b48e9ecdb6584c..eba0de1745243086bc03597d822ececb57386d00 100644
--- a/content/release/v2023pre.md
+++ b/content/release/v2023pre.md
@@ -6,3 +6,4 @@ title = "v2023pre"
# Release v2023pre
- {{< page-title-ref "/release/v2023pre/release_schedule.md" >}}
+- {{< page-title-ref "/release/v2023pre/releasenotes.md" >}}
\ No newline at end of file
diff --git a/content/release/v2023pre/releasenotes.md b/content/release/v2023pre/releasenotes.md
new file mode 100644
index 0000000000000000000000000000000000000000..75267364ae96a7bce69840c7505c0b9b82059e1f
--- /dev/null
+++ b/content/release/v2023pre/releasenotes.md
@@ -0,0 +1,183 @@
++++
+date = "2022-12-07"
+weight = 100
+
+title = "v2023pre Release Notes"
++++
+
+Apertis is a Debian derivative distribution geared towards the creation
+of product-specific images for ARM (both the 32bit ARMv7 and 64-bit
+ARMv8 versions using the hardfloat ABI) and Intel x86-64 (64-bit)
+systems.
+
+**Apertis v2023pre** is the **preview** release of the Apertis
+v2023 stable release flow that will lead to the LTS **Apertis v2023.0**
+release in March 2023.
+
+This Apertis release is built on top of Debian Bullseye with several
+customizations. It currently ships with the Linux kernel 5.18.x series
+but later releases in the v2023 channel will track newer kernel versions
+up to the next LTS.
+
+Test results for the v2023pre release are available in the following
+test reports:
+
+ - [APT images](https://qa.apertis.org/report/v2023pre/20221123.0019/apt)
+ - [OSTree images](https://qa.apertis.org/report/v2023pre/20221123.0019/ostree)
+ - [NFS artifacts](https://qa.apertis.org/report/v2023pre/20221123.0019/nfs)
+ - [LXC containers](https://qa.apertis.org/report/v2023pre/20221123.0019/lxc)
+
+## Release flow
+
+ - 2021 Q4: v2023dev0
+ - 2022 Q1: v2023dev1
+ - 2022 Q2: v2023dev2
+ - 2022 Q3: v2023dev3
+ - **2022 Q4: v2023pre**
+ - 2023 Q1: v2023.0
+ - 2023 Q2: v2023.1
+ - 2023 Q3: v2023.2
+ - 2023 Q4: v2023.3
+ - 2024 Q1: v2023.4
+ - 2024 Q2: v2023.5
+ - 2024 Q3: v2023.6
+ - 2024 Q4: v2023.7
+
+### Release downloads
+
+| [Apertis v2023pre.0 images](https://images.apertis.org/release/v2023pre/) | | | | |
+| ------------------------------------------------------------------------- |-|-|-|-|
+| Intel 64-bit | [fixedfunction](https://images.apertis.org/release/v2023pre/v2023pre.0/amd64/fixedfunction/apertis_ostree_v2023pre-fixedfunction-amd64-uefi_v2023pre.0.img.gz) | [hmi](https://images.apertis.org/release/v2023pre/v2023pre.0/amd64/hmi/apertis_ostree_v2023pre-hmi-amd64-uefi_v2023pre.0.img.gz) | [base SDK](https://images.apertis.org/release/v2023pre/v2023pre.0/amd64/basesdk/apertis_v2023pre-basesdk-amd64-sdk_v2023pre.0.ova) | [SDK](https://images.apertis.org/release/v2023pre/v2023pre.0/amd64/sdk/apertis_v2023pre-sdk-amd64-sdk_v2023pre.0.ova)
+| ARM 32-bit (U-Boot) | [fixedfunction](https://images.apertis.org/release/v2023pre/v2023pre.0/armhf/fixedfunction/apertis_ostree_v2023pre-fixedfunction-armhf-uboot_v2023pre.0.img.gz) | [hmi](https://images.apertis.org/release/v2023pre/v2023pre.0/armhf/hmi/apertis_ostree_v2023pre-hmi-armhf-uboot_v2023pre.0.img.gz)
+| ARM 64-bit (U-Boot) | [fixedfunction](https://images.apertis.org/release/v2023pre/v2023pre.0/arm64/fixedfunction/apertis_ostree_v2023pre-fixedfunction-arm64-uboot_v2023pre.0.img.gz)
+| ARM 64-bit (Raspberry Pi) | [fixedfunction](https://images.apertis.org/release/v2023pre/v2023pre.0/arm64/fixedfunction/apertis_ostree_v2023pre-fixedfunction-arm64-rpi64_v2023pre.0.img.gz) | [hmi](https://images.apertis.org/release/v2023pre/v2023pre.0/arm64/hmi/apertis_ostree_v2023pre-hmi-arm64-rpi64_v2023pre.0.img.gz)
+
+The Intel `fixedfunction` and `hmi` images are tested on the
+[reference hardware (UP Squared 6000)]( {{< ref "/reference_hardware/amd64.md" >}} ),
+but they can run on any UEFI-based x86-64 system. The `sdk` image is
+[tested under VirtualBox]( {{< ref "/virtualbox.md" >}} ).
+
+#### Apertis v2023pre package list
+
+The full list of packages available from the v2023pre APT repositories is available in tab-separated value (TSV) format for easy processing in spreadsheets:
+
+* [v2023pre](https://infrastructure.pages.apertis.org/dashboard/tsv/)
+
+#### Apertis v2023pre repositories
+
+ deb https://repositories.apertis.org/apertis/ v2023pre target development sdk
+
+## New features
+
+No new features since this is a preview release.
+
+## Build and integration
+
+### Improve QA Report App configuration and deployment
+
+### Improved QA Report App configuration management and deployment
+
+A set of changes were introduced to make configuring the QA Report App more straightforward and consistent, also including an improved validation of configuration settings.
+These improvements align with the use of **ansible** and **kubernetes** as a way to manage deployments and orchestration,
+improving automation and reducing manual work. These changes will also benefit downstream distributions, which will find it easier to deploy new instances.
+
+### QA Report App and OIDC authentication mechanism
+
+As a way to provide more flexibility around authentication mechanisms, the QA Report App now uses
+[OpenID Connect](https://openid.net/connect/) as the authentication mechanism, replacing the previous
+GitLab OAuth mechanism.
+
+Although the Apertis deployment still uses GitLab as the OIDC provider, this change will allow deployments to use
+any OIDC provider that best fit their needs.
+
+Relatedly, the QA Report App now also provides the support to always require login, allowing deployments to control
+whether login is required to access the reports.
+
+### Improved QA Report App support for weekly images
+
+Weekly Apertis images are tested with both automated and manual test cases, as part of the QA process.
+The results from these tests are submitted to the QA Report App, and now can be easily seen in the main page
+which provides a separate section for each type of image: releases, weeklies and dailies.
+
+## Deprecations and ABI/API breaks
+
+### Regressions
+
+No known regressions.
+
+### Deprecations
+
+No known deprecations
+
+### Breaks
+
+No know breaks
+
+## Infrastructure
+
+### Apertis Docker images
+
+The Apertis Docker images provide a unified and easily reproducible build
+environment for developers and services.
+
+As of today, this includes the
+[`apertis-base`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2023pre-base),
+[`apertis-image-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2023pre-image-builder),
+[`apertis-package-source-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2023pre-package-source-builder),
+[`apertis-flatdeb-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2023pre-flatdeb-builder),
+[`apertis-documentation-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2023pre-documentation-builder),
+and [`apertis-testcases-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2023pre-testcases-builder),
+Docker images.
+
+### Images
+
+Image daily builds, as well as release builds can be found at <https://images.apertis.org/>
+
+### Infrastructure overview
+
+The [Apertis Image Recipes](https://gitlab.apertis.org/infrastructure/apertis-image-recipes/)
+provides an overview of the image building process and the involved
+services.
+
+## Known issues
+
+### High
+- [Issue #122](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/122) aum-offline-upgrade: test failed
+- [Issue #126](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/126) aum-offline-upgrade-signed: test failed
+- [Issue #127](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/127) aum-api: test failed
+- [Issue #128](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/128) aum-ota-api: test failed
+- [Issue #134](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/134) aum-ota-signed: test failed
+- [Issue #146](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/146) aum-ota-out-of-space: test failed
+- [Issue #167](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/167) aum-ota-auto: test failed
+- [Issue #169](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/169) aum-out-of-space: test failed
+- [Issue #190](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/190) aum-power-cut: test failed
+- [Issue #203](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/203) aum-ota-rollback-blacklist: test failed
+- [Issue #204](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/204) aum-rollback-blacklist: test failed
+- [Issue #213](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/213) dbus-installed-tests: test failed
+- [Issue #215](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/215) Follow up FS corruption issue - part 2
+- [Issue #223](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/223) Launching an Application on agl-compositor takes more time
+- [Issue #224](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/224) SD card timeout issues in RPi4
+- [Issue #230](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/230) WebProcess CRASHED error is seen on executing webkit related testcases
+
+### Normal
+- [Issue #7](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/7) Crash when initialising egl on ARM target
+- [Issue #8](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/8) arm-linux-gnueabihf-pkg-config does not work with sysroots installed by `ade`
+- [Issue #12](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/12) gettext-i18n: test failed
+- [Issue #15](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/15) Fix the kernel command line generation in OSTRee for FIT image
+- [Issue #17](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/17) SabreLite failing to boot due to failing "to start udev Coldplug all Devices"
+- [Issue #22](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/22) debos sometimes fails to mount things
+- [Issue #26](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/26) newport: test failed
+- [Issue #32](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/32) Gitlab pipeline OBS job reported "success" but OBS build was "unresolvable"
+- [Issue #36](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/36) dashboard: gnome-settings-daemon-data incorrectly flagged as missing the git repository
+- [Issue #38](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/38) LAVA/Phab bridge timeouts
+- [Issue #39](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/39) grilo: test failed
+- [Issue #45](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/45) Manual testcase results should not have any hyperlink in the LavaPhabridge report page
+- [Issue #47](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/47) Failed to start Access poi…server : logs seen in v2023 amd64/armhf boot logs
+- [Issue #62](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/62) apparmor-ofono: test failed
+- [Issue #118](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/118) tiny-container-system-connectivity-profile: test failed
+- [Issue #119](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/119) tiny-container-user-connectivity-profile: test failed
+- [Issue #193](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/193) flatpak-run-demo-cli-app: test failed
+- [Issue #210](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/210) tiny-container-system-folder-sharing: test failed
+
+### Low
+- [Issue #23](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/23) Remote outputs and local output, buffer size combined in Maynard/GTK
\ No newline at end of file
diff --git a/data/releases.toml b/data/releases.toml
index 8d542f5bcf94bb8d7368ad0a212cde76362bfe1b..27752bc5738e73da4b8ac6da04231b60da8237ad 100644
--- a/data/releases.toml
+++ b/data/releases.toml
@@ -1,5 +1,5 @@
[Development]
-version = "v2023dev3"
+version = "v2023pre"
revision = "0"
[Stable]