Apertis has a three month release cycle. Development happens through most of the cycle with emphasis on bug fixing towards the end. The quarterly release cycle was chosen as it fits well with the fast paced development of Apertis.
Release timeline
The Apertis release cycle starts at the end of the previous release cycle. At this point, new features are proposed, discussed and implemented.
The soft feature freeze takes place about 2 weeks before the hard code freeze. Any features which you want to see in Apertis for the release need to be implemented in the source code before this date. From this date, only features which are already in Apertis can be polished for the release. This was previously known as “soft freeze”.
The hard feature freeze takes place about 1 week before the hard code freeze. At this point, only bug fixes can be made to Apertis code. This was previously known as “hard freeze”.
The hard code freeze takes places about 2 weeks before the stable release. All bugs considered release-blocker must be fixed before the bug fixing freeze. All development stops and the final image is prepared for the release. This was previously known as “bug fixing freeze”. As an outcome of the Release Candidate images are published for testing.
The RC testing takes place during the 2 weeks period after the hard code freeze. During this time QA team executes the test cases to confirm the good health of the release.
The final image is published on the release day.
If you need to request a break (exception) for any of the above freezes, you can do so by emailing the Apertis mailing list (devel@lists.apertis.org) and getting the support of two or more Apertis maintainers.
Releases
The latest releases are:
- v2026dev0: release notes, release schedule
- v2025pre: release notes, release schedule
- v2024.3: release notes, release schedule
- v2023.7: release notes, release schedule
The next releases will be:
- v2026dev1: release schedule
- v2025.0: release schedule
- v2024.4: release schedule
For previous releases see:
- v2025dev3: release notes, release schedule
- v2024.2: release notes, release schedule
- v2023.6: release notes, release schedule
- v2025dev2: release notes, release schedule
- v2024.1: release notes, release schedule
- v2023.5: release notes, release schedule
- v2025dev1: release notes, release schedule
- v2024.0: release notes, release schedule
- v2023.4: release notes, release schedule
- v2025dev0: release notes, release schedule
- v2024pre: release notes, release schedule
- v2023.3: release notes, release schedule
- v2022.7: release notes, release schedule
- v2024dev3: release notes, release schedule
- v2023.2: release notes, release schedule
- v2022.6: release notes, release schedule
- v2024dev2: release notes, release schedule
- v2023.1: release notes, release schedule
- v2022.5: release notes, release schedule
- v2024dev1: release notes, release schedule
- v2023.0: release notes, release schedule
- v2022.4: release notes, release schedule
- v2024dev0: release notes, release schedule
- v2023pre: release notes, release schedule
- v2022.3: release notes, release schedule
- v2021.7: release notes, release schedule
- v2023dev3: release notes, release schedule
- v2022.2: release notes, release schedule
- v2021.6: release notes, release schedule
- v2023dev2: release notes, release schedule
- v2022.1: release notes, release schedule
- v2021.5: release notes, release schedule
- v2023dev1: release notes, release schedule
- v2022.0: release notes, release schedule
- v2021.4: release notes, release schedule
- v2023dev0: release notes, release schedule
- v2022pre: release notes, release schedule
- v2021.3: release notes, release schedule
- v2020.7: release notes, release schedule
- v2022dev3: release notes, release schedule
- v2021.2: release notes, release schedule
- v2020.6: release notes, release schedule
- v2022dev2: release notes, release schedule
- v2021.1: release notes, release schedule
- v2020.5: release notes, release schedule
- v2022dev1: release notes, release schedule
- v2019.7: release notes, release schedule
- v2021.0: release notes, release schedule
- v2020.4: release notes, release schedule
- v2019.6: release notes, release schedule
- v2022dev0: release notes, release schedule
- v2021pre: release notes, release schedule
- v2020.3: release notes, release schedule
- v2019.5: release notes, release schedule
- v2021dev3: release notes, release schedule
- v2020.2: release notes, release schedule
- v2019.4: release notes, release schedule
- v2021dev2: release notes, release schedule
- v2020.1: release notes, release schedule
- v2019.3: release notes, release schedule
- v2021dev1: release notes, release schedule
- v2020.0: release notes, release schedule
- v2019.2: release notes, release schedule
- v2020pre: release notes, release schedule
- v2019.1: release notes, release schedule
- v2020dev0: release notes, release schedule
- v2019.0: release notes, release schedule
- v2019pre: release notes, release schedule
- v2019dev0: release notes, release schedule
- 18.12: release notes, release schedule
- 18.09: release notes, release schedule
- 18.06: release notes, release schedule
- 18.03: release notes, release schedule
- 17.12.1: release notes
- 17.12: release notes, release schedule
- 17.09: release notes, release schedule
- 17.06: release notes, release schedule
- 17.03: release notes, release schedule
- 16.12: release notes, release schedule
- 16.09: release notes, release schedule
- 16.06: release notes, release schedule
- 16.03: release notes, release schedule
- 15.12: release notes
- 15.09: release notes
- 15.06: release notes
- 15.03: release notes
- 14.12: release notes
Security support
- When a release happens it automatically supersedes the previous release, therefore previous releases are discontinued and do not receive any security support.
- Superseded releases shall be removed from Apertis build infrastructure a short time after the current release.