Google Reduces AOSP Code Releases to Twice Yearly, Mandates Development Adjustments

Google has confirmed a reduction in Android Open Source Project (AOSP) code releases from quarterly to twice annually. This change takes effect in 2026. Releases will occur in Q2 and Q4.

This adjustment aligns with Google's trunk stable development model. The company states it will enhance platform stability and security. Developers must now integrate major code updates twice yearly instead of four times. Security updates remain unaffected and will continue on a separate, frequent schedule.

Organizations building Android-compatible systems must modify development timelines. Projects should allocate resources for integration during Q2 and Q4. This consolidation eliminates multiple code branch management. Google asserts it allows more thorough testing and secure code delivery.

Concurrently, Google's developer registration requirements for app installations create compliance considerations. These rules, announced in 2025, conflict with open-source distribution models like F-Droid. Entities using alternative app marketplaces must evaluate registration compliance or alternative distribution methods.

Compliance teams should audit Android integration processes. They must ensure alignment with the 2026 release schedule and address any conflicts with app distribution frameworks.