v2025dev1 release notes

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

v2025dev1 release notes
af9ac7ca · Walter Lozano · 3aaf7e2a · af9ac7ca · af9ac7ca · af9ac7ca
Commit af9ac7ca authored Mar 11, 2024 by Walter Lozano
--- a/content/_index.md
+++ b/content/_index.md
@@ -89,7 +89,7 @@ year.
 * [Release Schedule]( {{< ref "releases.md" >}} )
 * Current stable release: [v2024.0]( {{< ref "/release/v2024.0/releasenotes.md" >}} )
 * Current old stable release: [v2023.4]( {{< ref "/release/v2023.4/releasenotes.md" >}} )
-* Current development release: [v2025dev0]( {{< ref "/release/v2025dev0/releasenotes.md" >}} )
+* Current development release: [v2025dev1]( {{< ref "/release/v2025dev1/releasenotes.md" >}} )
 {{% /link-box %}}
 {{% /homepage-column %}}



--- 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:

-  - v2025dev0: [release notes]( {{< ref "/release/v2025dev0/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2025dev0/release_schedule.md" >}} )
+  - v2025dev1: [release notes]( {{< ref "/release/v2025dev1/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2025dev1/release_schedule.md" >}} )
  - v2024.0: [release notes]( {{< ref "/release/v2024.0/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2024.0/release_schedule.md" >}} )
  - v2023.4: [release notes]( {{< ref "/release/v2023.4/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2023.4/release_schedule.md" >}} )

 The next releases will be:

-  - v2025dev1: [release schedule]( {{< ref "/release/v2025dev1/release_schedule.md" >}} )
+  - v2025dev2: [release schedule]( {{< ref "/release/v2025dev2/release_schedule.md" >}} )
  - v2024.1: [release schedule]( {{< ref "/release/v2024.1/release_schedule.md" >}} )
  - v2023.5: [release schedule]( {{< ref "/release/v2023.5/release_schedule.md" >}} )

 For previous releases see:
+  - v2025dev0: [release notes]( {{< ref "/release/v2025dev0/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2025dev0/release_schedule.md" >}} )
  - v2024pre: [release notes]( {{< ref "/release/v2024pre/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2024pre/release_schedule.md" >}} )
  - v2023.3: [release notes]( {{< ref "/release/v2023.3/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2023.3/release_schedule.md" >}} )
  - v2022.7: [release notes]( {{< ref "/release/v2022.7/releasenotes.md" >}} ), [release schedule]( {{< ref "/release/v2022.7/release_schedule.md" >}} )


--- a/content/release/v2025dev1.md
+++ b/content/release/v2025dev1.md
@@ -6,3 +6,4 @@ title = "v2025dev1"
 # Release v2025dev1

 - {{< page-title-ref "/release/v2025dev1/release_schedule.md" >}}
+- {{< page-title-ref "/release/v2025dev1/releasenotes.md" >}}
\ No newline at end of file
--- a/content/release/v2025dev1/releasenotes.md
+++ b/content/release/v2025dev1/releasenotes.md
+++
+date = "2024-03-13"
+weight = 100
+
+title = "v2025dev1 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 v2025dev1** is the second development release of the Apertis
+v2025 stable release flow that will lead to the LTS **Apertis v2025.0**
+release in March 2025.
+
+This Apertis release is built on top of Debian Bookworm along with several customizations
+and it ships the latest Linux kernel 6.6.x series. Later releases in the v2025 channel
+will be tracking newer kernel versions up to the next LTS as well as Debian Bookworm
+Stable Channel.
+
+Test results for the v2025dev1 release are available in the following
+test reports:
+
+  - [APT images](https://qa.apertis.org/report/v2025dev1/20240228.0017/apt)
+  - [OSTree images](https://qa.apertis.org/report/v2025dev1/20240228.0017/ostree)
+  - [NFS artifacts](https://qa.apertis.org/report/v2025dev1/20240228.0017/nfs)
+  - [LXC containers](https://qa.apertis.org/report/v2025dev1/20240228.0017/lxc)
+
+## Release flow
+
+  - 2023 Q4: v2025dev0
+  - 2024 Q1: **v2025dev1**
+  - 2024 Q2: v2025dev2
+  - 2024 Q3: v2025dev3
+  - 2024 Q4: v2025pre
+  - 2025 Q1: v2025.0
+  - 2025 Q2: v2025.1
+  - 2025 Q3: v2025.2
+  - 2025 Q4: v2025.3
+  - 2026 Q1: v2025.4
+  - 2026 Q2: v2025.5
+  - 2026 Q3: v2025.6
+  - 2026 Q4: v2025.7
+
+### Release downloads
+
+| [Apertis v2025dev1.0 images](https://images.apertis.org/release/v2025dev1/) | | | | |
+| ------------------------------------------------------------------------- |-|-|-|-|
+| Intel 64-bit		| [fixedfunction](https://images.apertis.org/release/v2025dev1/v2025dev1.0/amd64/fixedfunction/apertis_ostree_v2025dev1-fixedfunction-amd64-uefi_v2025dev1.0.img.gz) | [hmi](https://images.apertis.org/release/v2025dev1/v2025dev1.0/amd64/hmi/apertis_ostree_v2025dev1-hmi-amd64-uefi_v2025dev1.0.img.gz) | [base SDK](https://images.apertis.org/release/v2025dev1/v2025dev1.0/amd64/basesdk/apertis_v2025dev1-basesdk-amd64-sdk_v2025dev1.0.ova) | [SDK](https://images.apertis.org/release/v2025dev1/v2025dev1.0/amd64/sdk/apertis_v2025dev1-sdk-amd64-sdk_v2025dev1.0.ova)
+| ARM 32-bit (U-Boot)	| [fixedfunction](https://images.apertis.org/release/v2025dev1/v2025dev1.0/armhf/fixedfunction/apertis_ostree_v2025dev1-fixedfunction-armhf-uboot_v2025dev1.0.img.gz) | [hmi](https://images.apertis.org/release/v2025dev1/v2025dev1.0/armhf/hmi/apertis_ostree_v2025dev1-hmi-armhf-uboot_v2025dev1.0.img.gz)
+| ARM 64-bit (U-Boot)	| [fixedfunction](https://images.apertis.org/release/v2025dev1/v2025dev1.0/arm64/fixedfunction/apertis_ostree_v2025dev1-fixedfunction-arm64-uboot_v2025dev1.0.img.gz)
+| ARM 64-bit (Raspberry Pi)	| [fixedfunction](https://images.apertis.org/release/v2025dev1/v2025dev1.0/arm64/fixedfunction/apertis_ostree_v2025dev1-fixedfunction-arm64-rpi64_v2025dev1.0.img.gz) | [hmi](https://images.apertis.org/release/v2025dev1/v2025dev1.0/arm64/hmi/apertis_ostree_v2025dev1-hmi-arm64-rpi64_v2025dev1.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 v2025dev1 package list
+
+The full list of packages available from the v2025dev1 APT repositories is available in tab-separated value (TSV) format for easy processing in spreadsheets:
+
+* [v2025dev1](https://infrastructure.pages.apertis.org/dashboard/tsv/v2025dev1.tsv)
+
+#### Apertis v2025dev1 repositories
+
+    deb https://repositories.apertis.org/apertis/ v2025dev1 target development sdk non-free
+
+## New features
+
+### Additional compiler warnings enabled by default
+
+This new releases includes an Apertis specific profile for `dpkg` to enable additional compiler warnings.
+The use of this warnings can help to spot potential security issues in the packages being built,
+improving the quality of the system.
+
+## Build and integration
+
+### Add support for package testing
+
+This release includes a new way for developers to includes tests to run on a Merge Request.
+The [package testing in LAVA]({{< ref "apertis-packages-testing.md" >}}) allows writing tests a part of the
+standard packing metadata, which are used by our GitLab infrastructure to run LAVA tests to
+ensure the proposed changes do not introduce any kind of regression in the supported hardware.
+
+### Support for image change history
+
+Apertis now provides [Change History Generator](https://gitlab.apertis.org/infrastructure/change-history-generator/)
+a tool to generate a changelog between images. Thanks to this tool, as part of
+[daily builds](https://images.apertis.org/daily/v2024/) a
+[changelog](https://images.apertis.org/release/v2024/v2024.0/amd64/fixedfunction/ospack_v2024-amd64-fixedfunction_v2024.0.changelogs.tar.gz)
+is created which helps developers to track changes across different images.
+
+## 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/v2025dev1-base),
+[`apertis-image-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2025dev1-image-builder),
+[`apertis-package-source-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2025dev1-package-source-builder),
+[`apertis-flatdeb-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2025dev1-flatdeb-builder),
+[`apertis-documentation-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2025dev1-documentation-builder),
+and [`apertis-testcases-builder`](docker://registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2025dev1-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 #339](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/339) Up Squared 6000 board fails to boot randomly in LAVA
+- [Issue #363](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/363) aum-ota-rollback-blacklist: test failed
+- [Issue #364](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/364) aum-offline-upgrade-branch: test failed
+- [Issue #431](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/431) Package rust-coreutils does not provide license mapping information
+- [Issue #437](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/437) Weekly images are not linked properly
+- [Issue #438](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/438) pstore-test case is getting failed in armhf
+- [Issue #451](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/451) dbus-installed-tests: test failed
+- [Issue #456](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/456) SBOM support for rust packages does not work in v2024pre
+- [Issue #466](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/466) AUM out of space tests fail sporadically
+- [Issue #469](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/469) aum-power-cut: test failed
+- [Issue #474](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/474) "WiFi WPA3-Transition-Mode access point" (AP mode) connection is not re-established after rebooting AP.
+- [Issue #476](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/476) "apertis-update-manager-usb-unplug" is getting failed. Update is not starting automatically
+- [Issue #480](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/480) aum-ota-api: test failed
+- [Issue #485](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/485) AUM tests fail on v2024 and v2025dev* armhf- [Issue #490](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/490) gpgv (sequioa) crashes when added debian archives
+- [Issue #514](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/514) aum-out-of-space: test failed
+- [Issue #523](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/523) Dev package name showing inside the target on target source list
+- [Issue #524](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/524) connman: test failed
+- [Issue #526](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/526) Package centric testing does not work with OSTree images
+- [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 #530](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/530) aum-ota-out-of-space: test failed
+- [Issue #531](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/531) aum-api: test failed
+- [Issue #532](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/532) AUM offline upgrade branch fails on RPi4
+- [Issue #535](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/535) aum-ota-signed: test failed
+- [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
+
+### Normal
+- [Issue #7](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/7) Crash when initialising egl on ARM target
+- [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 #118](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/118) tiny-container-system-connectivity-profile: test failed
+- [Issue #246](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/246) tiny-container-user-connectivity-profile: test failed
+- [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 #322](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/322) wrap-and-sort fails to parse some debian/control.in files
+- [Issue #330](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/330) datefudge: 64-bit time_t support on 32-bit archs
+- [Issue #338](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/338) psdk-test not executing properly.
+- [Issue #354](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/354) apparmor utils test shows as incomplete
+- [Issue #376](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/376) apparmor functional demo reports errors
+- [Issue #377](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/377) import-debian-package issues during package import
+- [Issue #378](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/378) apparmor-gstreamer1-0: test failed
+- [Issue #396](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/396) Pipeline to build package fails during build-source for texlive-extra
+- [Issue #397](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/397) Pipeline to import new version of plotly from Bookworm fails during pull-updates
+- [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 #486](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/486) "webkit2gtk-ac-3d-rendering" fails in "ARMHF".
+- [Issue #488](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/488) Flashing an HMI image on the eMMC of R-car H3e-2G board leads to a kernel panic.
+- [Issue #491](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/491) AM62x: Do not install firmware prerequisites in image for boot firmware generation
+- [Issue #502](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/502) tiny-container connectivity-profile: test failed
+- [Issue #508](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/508) sdk-import-debian-package: test failed
+- [Issue #513](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/513) apparmor-ofono: test failed
+- [Issue #525](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/525) RPi image list points to v2022 instead of daily development images
+- [Issue #539](https://gitlab.apertis.org/infrastructure/apertis-issues/-/issues/539) Create automatic sdk tests in apertis-test-cases for abi-checker job
+
+### 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
+
--- a/content/release/v2025dev2.md
+++ b/content/release/v2025dev2.md
+++
+weight = 100
+title = "v2025dev2"
+++
+
+# Release v2025dev2
+
+- {{< page-title-ref "/release/v2025dev2/release_schedule.md" >}}
--- a/content/release/v2025dev2/release_schedule.md
+++ b/content/release/v2025dev2/release_schedule.md
+++
+date = "2024-03-11"
+weight = 100
+
+title = "v2025dev2 Release schedule"
+++
+
+The v2025dev2 release cycle is scheduled to start in January 2024.
+
+| Milestone                                                                                                | Date              |
+| -------------------------------------------------------------------------------------------------------- | ----------------- |
+| Start of release cycle                                                                                   | 2024-04-01        |
+| Soft feature freeze: end of feature proposal and review period                                           | 2024-05-15        |
+| Soft code freeze/hard feature freeze: end of feature development for this release, only bugfixes allowed | 2024-05-22        |
+| Release candidate 1 (RC1)/hard code freeze: no new code changes may be made after this date              | 2024-05-29        |
+| RC testing                                                                                               | 2024-05-30..06-12 |
+| v2025dev2 release                                                                                        | 2024-06-13        |
+
+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