diff --git a/content/_index.md b/content/_index.md
index 32f610a9dd3f9f20d523fd2d442fe4b3bce2163a..d5ee773370aaf3a15d3edd18c3bf33c8ac6c5744 100644
--- a/content/_index.md
+++ b/content/_index.md
@@ -90,7 +90,7 @@ year.
* [Release Schedule]( {{< ref "releases.md" >}} )
* Current stable release: [v2025.0]( {{< ref "/release/v2025/v2025.0/releasenotes.md" >}} )
* Current old stable release: [v2024.4]( {{< ref "/release/v2024/v2024.4/releasenotes.md" >}} )
-* Current development release: [v2026dev0]( {{< ref "/release/v2026/v2026dev0/releasenotes.md" >}} )
+* Current development release: [v2026dev1]( {{< ref "/release/v2026/v2026dev1/releasenotes.md" >}} )
{{% /link-box %}}
{{% /homepage-column %}}
diff --git a/content/policies/releases.md b/content/policies/releases.md
index 8fa395ad1034646e7a8dbea9eaa5c59e4d128116..d47f3ec1c9df8d066d8f3f0cc2c618dcfb21043a 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:
- - v2026dev0: [release notes]( {{< ref "/release/v2026/v2026dev0/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2026/v2026dev0/release_schedule.md" >}} )
+ - v2026dev1: [release notes]( {{< ref "/release/v2026/v2026dev1/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2026/v2026dev1/release_schedule.md" >}} )
- v2025.0: [release notes]( {{< ref "/release/v2025/v2025.0/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2025/v2025.0/release_schedule.md" >}} )
- v2024.4: [release notes]( {{< ref "/release/v2024/v2024.4/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2024/v2024.4/release_schedule.md" >}} )
The next releases will be:
- - v2026dev1: [release schedule]( {{< ref "/release/v2026/v2026dev1/release_schedule.md" >}} )
+ - v2026dev2: [release schedule]( {{< ref "/release/v2026/v2026dev2/release_schedule.md" >}} )
- v2025.1: [release schedule]( {{< ref "/release/v2025/v2025.1/release_schedule.md" >}} )
- v2024.5: [release schedule]( {{< ref "/release/v2024/v2024.5/release_schedule.md" >}} )
For previous releases see:
+ - v2026dev0: [release notes]( {{< ref "/release/v2026/v2026dev0/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2026/v2026dev0/release_schedule.md" >}} )
- v2025pre: [release notes]( {{< ref "/release/v2025/v2025pre/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2025/v2025pre/release_schedule.md" >}} )
- v2023.7: [release notes]( {{< ref "/release/v2023/v2023.7/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2023/v2023.7/release_schedule.md" >}} )
- v2024.3: [release notes]( {{< ref "/release/v2024/v2024.3/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2024/v2024.3/release_schedule.md" >}} )\
diff --git a/content/release/v2026/v2026dev1/releasenotes.md b/content/release/v2026/v2026dev1/releasenotes.md
new file mode 100644
index 0000000000000000000000000000000000000000..4704363ca186854f04aa8b618d45ef1ded78ee48
--- /dev/null
+++ b/content/release/v2026/v2026dev1/releasenotes.md
@@ -0,0 +1,197 @@
++++
+date = "2025-03-13"
+weight = 100
+
+title = "v2026dev1 Release Notes"
+
+aliases = [
+ "/release/v2026dev1/releasenotes",
+]
++++
+
+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 v2026dev1** is the second development release of the Apertis
+v2026 stable release flow that will lead to the LTS **Apertis v2026.0**
+release in March 2026.
+
+This Apertis release is built on top of Debian Bookworm along with several customizations
+and it ships the latest Linux kernel 6.12.x series. Later releases in the v2026 channel
+will be tracking Debian Trixie and newer kernel versions.
+
+Test results for the v2026dev1 release are available in the following
+test reports:
+
+ - [APT images](https://qa.apertis.org/report/v2026dev1/20250226.0017/apt)
+ - [OSTree images](https://qa.apertis.org/report/v2026dev1/20250226.0017/ostree)
+ - [NFS artifacts](https://qa.apertis.org/report/v2026dev1/20250226.0017/nfs)
+ - [LXC containers](https://qa.apertis.org/report/v2026dev1/20250226.0017/lxc)
+
+Since this release is the development last before the rebase on top of Debian Trixie
+no manual testing has been performed.
+
+## Release flow
+
+ - 2024 Q4: v2026dev0
+ - 2025 Q1: **v2026dev1**
+ - 2025 Q2: v2026dev2
+ - 2025 Q3: v2026dev3
+ - 2025 Q4: v2026pre
+ - 2026 Q1: v2026.0
+ - 2026 Q2: v2026.1
+ - 2026 Q3: v2026.2
+ - 2026 Q4: v2026.3
+ - 2027 Q1: v2026.4
+ - 2027 Q2: v2026.5
+ - 2027 Q3: v2026.6
+ - 2027 Q4: v2026.7
+
+### Release downloads
+
+| [Apertis v2026dev1.0 images](https://images.apertis.org/release/v2026dev1/) | | | | |
+| ------------------------------------------------------------------------- |-|-|-|-|
+| Intel 64-bit | [fixedfunction](https://images.apertis.org/release/v2026dev1/v2026dev1.0/amd64/fixedfunction/apertis_ostree_v2026dev1-fixedfunction-amd64-uefi_v2026dev1.0.img.gz) | [hmi](https://images.apertis.org/release/v2026dev1/v2026dev1.0/amd64/hmi/apertis_ostree_v2026dev1-hmi-amd64-uefi_v2026dev1.0.img.gz) | [base SDK](https://images.apertis.org/release/v2026dev1/v2026dev1.0/amd64/basesdk/apertis_v2026dev1-basesdk-amd64-sdk_v2026dev1.0.ova) | [SDK](https://images.apertis.org/release/v2026dev1/v2026dev1.0/amd64/sdk/apertis_v2026dev1-sdk-amd64-sdk_v2026dev1.0.ova)
+| ARM 32-bit (U-Boot) | [fixedfunction](https://images.apertis.org/release/v2026dev1/v2026dev1.0/armhf/fixedfunction/apertis_ostree_v2026dev1-fixedfunction-armhf-uboot_v2026dev1.0.img.gz) | [hmi](https://images.apertis.org/release/v2026dev1/v2026dev1.0/armhf/hmi/apertis_ostree_v2026dev1-hmi-armhf-uboot_v2026dev1.0.img.gz)
+| ARM 64-bit (U-Boot) | [fixedfunction](https://images.apertis.org/release/v2026dev1/v2026dev1.0/arm64/fixedfunction/apertis_ostree_v2026dev1-fixedfunction-arm64-uboot_v2026dev1.0.img.gz)
+| ARM 64-bit (Raspberry Pi) | [fixedfunction](https://images.apertis.org/release/v2026dev1/v2026dev1.0/arm64/fixedfunction/apertis_ostree_v2026dev1-fixedfunction-arm64-rpi64_v2026dev1.0.img.gz) | [hmi](https://images.apertis.org/release/v2026dev1/v2026dev1.0/arm64/hmi/apertis_ostree_v2026dev1-hmi-arm64-rpi64_v2026dev1.0.img.gz)
+
+The Intel `fixedfunction` and `hmi` images are tested on the
+[reference hardware (UP Squared 6000)]( {{< ref "amd64.md" >}} ),
+but they can run on any UEFI-based x86-64 system. The `sdk` image is
+[tested under VirtualBox]( {{< ref "virtualbox.md" >}} ).
+
+#### Apertis v2026dev1 package list
+
+The full list of packages available from the v2026dev1 APT repositories is available in tab-separated value (TSV) format for easy processing in spreadsheets:
+
+* [v2026dev1](https://infrastructure.pages.apertis.org/dashboard/tsv/v2026dev1.tsv)
+
+#### Apertis v2026dev1 repositories
+
+ deb https://repositories.apertis.org/apertis/ v2026dev1 target development sdk non-free
+
+## New features
+
+No new features have been introduced
+
+## Build and integration
+
+### Rust an Go packages moved to target
+
+To align with Apertis policies Rust and Go packages used to build packages in target were moved
+from development to target. In this way, code that is intended to be used in target devices lives
+in target where compliance checks are performed. This change was needed, since these languages are
+statically linked, causing that most of the build dependencies ship code that is used in the binaries.
+
+### Folding and branching pipeline improvements
+
+The folding and branching process has been moved to Gitlab CI, but the work continues to
+make these pipelines more developer and user friendly. With this idea in mind the code has
+been refactored to improve consistency and make it easier to maintain and debug. From the
+user perspective, the new version provides more hints to and checks to avoid mistakes and
+improve debug information.
+
+## Deprecations and ABI/API breaks
+
+### Regressions
+
+No known regressions.
+
+### Deprecations
+
+No known deprecations
+
+### Breaks
+
+No known 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/v2026dev1-base),
+[`apertis-image-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2026dev1-image-builder),
+[`apertis-package-source-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2026dev1-package-source-builder),
+[`apertis-flatdeb-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2026dev1-flatdeb-builder),
+[`apertis-documentation-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2026dev1-documentation-builder),
+and [`apertis-testcases-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2026dev1-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 #419](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/419) High level tracking of AUM issues
+- [Issue #615](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/615) aum-offline-upgrade-branch: test failed
+- [Issue #636](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/636) WiFi connection does not bring up after reboot
+- [Issue #695](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/695) aum-rollback-bootcount: error message displayed during the test
+- [Issue #731](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/731) Investigate license issue with golang-github-juju-ratelimit and golang-github-juju-ansiterm
+- [Issue #736](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/736) OBS: the build of some packages disturbs OBS behaviour
+- [Issue #752](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/752) Unable to test audio policies in armhf
+
+### Normal
+- [Issue #7](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/7) Crash when initialising egl on ARM target
+- [Issue #9](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/9) System users are shipped in /usr/etc/passwd instead of /lib/passwd
+- [Issue #32](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/32) Gitlab pipeline OBS job reported "success" but OBS build was "unresolvable"
+- [Issue #49](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/49) "firmware: failed to load" logs seen during boot
+- [Issue #66](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/66) Some binaries in the toolchain tarball are huge
+- [Issue #256](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/256) OBS: Backend doesn’t start immediately upon restart
+- [Issue #273](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/273) Debos build output hidden on GitLab job view can only be seen in the raw log file
+- [Issue #331](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/331) Frequent 504 Errors repeatedly causing pipelines to be marked as failed
+- [Issue #339](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/339) Up Squared 6000 board fails to boot randomly in LAVA
+- [Issue #377](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/377) import-debian-package issues during package import
+- [Issue #396](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/396) Pipeline to build package fails during build-source for texlive-extra
+- [Issue #405](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/405) traprain: test failed
+- [Issue #413](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/413) obs-runner: Disabled architectures on a OBS package get re-enabled when CI creates a branch
+- [Issue #441](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/441) tiny-container-user-device-sharing: test failed
+- [Issue #448](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/448) ade-commands: test failed
+- [Issue #459](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/459) tiny-container-system-device-sharing: test failed
+- [Issue #462](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/462) agl-compositor mute functionality not working
+- [Issue #486](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/486) "webkit2gtk-ac-3d-rendering" fails in "ARMHF".
+- [Issue #490](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/490) gpgv (sequioa) crashes when added debian archives
+- [Issue #528](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/528) OBS runner creates conflicts in the origin repo, then waits forever for them
+- [Issue #537](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/537) Update some apertis gitlab-ci pipeline to use a bookworm image instead of a bullseye/buster image
+- [Issue #597](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/597) obs runner is confused by multple OBS repos
+- [Issue #602](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/602) lintian: the child pipeline lintian-errors is always triggered on the default branch instead of the same branch as the parent job
+- [Issue #603](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/603) AUM upgrade branch fails on amd64 on all releases
+- [Issue #633](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/633) dashboard: issues just after a branching
+- [Issue #637](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/637) Improve the repo/pipeline used to test the lintian job
+- [Issue #638](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/638) Improve the repos/pipelines used to test the abi-checker job
+- [Issue #639](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/639) apertis-dev depends on eatmydata that was dropped during the rebase on Bookworm
+- [Issue #643](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/643) Improve the tool import-debian-package to trigger the generation of debian/apertis/copyright on an initial import.
+- [Issue #656](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/656) Improve apertis-pkg-* tools (from apertis-dev-tools) to use python-gitlab instead of relying on urllib
+- [Issue #659](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/659) Remove "hmi" repository from website documentation
+- [Issue #664](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/664) Improve workflow for importing packages
+- [Issue #665](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/665) Write a python tool to generate apertis-oslist.json (for rpi-imager)
+- [Issue #675](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/675) pkg/debugpy: investigate tests failure at build time
+- [Issue #678](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/678) Test pipeline of ci-flatdeb-builder triggers too many (5) MR pipelines
+- [Issue #691](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/691) tiny-container-system-connectivity-profile: test failed
+- [Issue #692](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/692) tiny-container-user-connectivity-profile: test failed
+- [Issue #702](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/702) Improve delta tracking in linux package
+- [Issue #703](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/703) Add recommendations about gitignore usage
+- [Issue #721](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/721) Improve checks on folding/branching
+- [Issue #734](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/734) qa-parser relies on lqa which is unmaintained
+- [Issue #742](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/742) dashboard reports Git repository contains an untracked debian branch debian/bullseye
+
+### Low
+- [Issue #15](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/15) Fix the kernel command line generation in OSTRee for FIT image
+- [Issue #23](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/23) Remote outputs and local output, buffer size combined in Maynard/GTK
+- [Issue #65](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/65) Terminal at xfce desktop corrupted after debos call
+- [Issue #607](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/607) Pipeline for sample application helloworld-https-client fails
+
diff --git a/content/release/v2026/v2026dev2.md b/content/release/v2026/v2026dev2.md
new file mode 100644
index 0000000000000000000000000000000000000000..4da75401dbaa40e41bf94c4ba62b80582a1c5ae6
--- /dev/null
+++ b/content/release/v2026/v2026dev2.md
@@ -0,0 +1,12 @@
++++
+weight = 100
+title = "v2026dev2"
+
+aliases = [
+ "/release/v2026dev2",
+]
++++
+
+# Release v2026dev2
+
+{{< section-toc >}}
diff --git a/content/release/v2026/v2026dev2/release_schedule.md b/content/release/v2026/v2026dev2/release_schedule.md
new file mode 100644
index 0000000000000000000000000000000000000000..396a69a3c977f1f25f3fa32a48b0f67a817aa3f7
--- /dev/null
+++ b/content/release/v2026/v2026dev2/release_schedule.md
@@ -0,0 +1,31 @@
++++
+date = "2025-03-13"
+weight = 100
+
+title = "v2026dev2 Release schedule"
+
+aliases = [
+ "/release/v2026dev2/release_schedule",
+]
++++
+
+The v2026dev2 release cycle is scheduled to start in January 2025.
+
+| Milestone | Date |
+| -------------------------------------------------------------------------------------------------------- | ----------------- |
+| Start of release cycle | 2025-04-01 |
+| Soft feature freeze: end of feature proposal and review period | 2025-05-14 |
+| Soft code freeze/hard feature freeze: end of feature development for this release, only bugfixes allowed | 2025-05-21 |
+| Release candidate 1 (RC1)/hard code freeze: no new code changes may be made after this date | 2025-05-28 |
+| RC testing | 2025-05-29..06-11 |
+| v2026dev2 release | 2025-06-12 |
+
+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/data/releases.toml b/data/releases.toml
index f360ddd6e1b1707a3a1f3d499a87aa579487dbd0..9f66fa103a820bae06f38bbbd6e34dd394093eb5 100644
--- a/data/releases.toml
+++ b/data/releases.toml
@@ -1,5 +1,5 @@
[Development]
-version = "v2026dev0"
+version = "v2026dev1"
revision = "0"
[Stable]