Google announced a significant change in the Android Open Source Project (AOSP) source code release schedule, going from four to just two releases per year starting in 2026. The company will concentrate publications in the second and fourth quarters, prioritizing updates considered most relevant to the development of the platform.
This change aims to align the process with the trunk-stable development model, which seeks greater stability for the entire Android ecosystem. A warning already appears on the official AOSP website, recommending that developers use the android-latest-release branch instead of the traditional aosp-main.
The decision does not affect the distribution of monthly security patches, which will continue to be released regularly in a dedicated branch.
Reasons for the change in schedule
Google explained that the previous cadence, with quarterly releases, increased internal complexity by requiring the management of multiple branches of code simultaneously. Essa approach made it difficult to maintain coherence and security across versions.
By scaling back to two annual releases, the company aims to provide a more predictable and solid foundation for device makers and developers. The concentration in Q2 and Q4 corresponds to the major mid-year updates and the smaller end-of-year updates, which generally bring more impactful changes to the platform.
Recommendations for developers
Developers building or contributing to AOSP should migrate to the new android-latest-release branch. Esse branch will always point to the latest publicly published version, avoiding dependency on aosp-main, which will no longer reflect the real-time state of the project.
This transition makes it easier to work with a stable version, reducing the risk of instability in custom builds. Google reinforces that the change simplifies the development flow without compromising access to open source.
Maintaining security updates
Monthly security patches will remain unchanged, being published in a specific branch as is currently the case. Essa separation ensures that Android devices continue to receive vulnerability fixes on a regular basis, regardless of the full source code schedule.
Partner manufacturers, such as large ones, already receive early access to private codes, which does not change their development pipelines.
New trunk-stable model in detail
The trunk-stable model adopts a single development trunk, with features activated by flags until they are ready for general use. Essa strategy avoids excessive branching and promotes a more uniform foundation for the entire ecosystem.
- Reduces complexity in managing parallel branches.
- Increases predictability for OEMs and custom ROM communities.
- Maintains focus on releases with relevant changes for developers.
- It preserves its commitment to open source, according to the company.
This approach was already being implemented gradually, with delays observed in some 2025 releases.
Effects on the ecosystem
The change may require adjustments to projects that rely on frequent access to the latest code, such as custom ROM communities. However, Google argues that less frequent but more consolidated releases result in more mature and secure code.
For end users, the impact is minimal, as system updates come directly from manufacturers. The platform’s greater stability can benefit fragmentation and the delivery of features across different devices in the long term.
Prospects for future development
With the new pace, Q2 should bring the big annual update, while Q4 will focus on refinements with new APIs. Essa concentration allows Google to deliver more tested versions, aligning with competitor practices that prioritize robust annual cycles.
The Android ecosystem, which powers billions of devices globally, benefits from a more controlled foundation. Independent Desenvolvedores will need to plan for longer cycles but rely on ongoing security patches.