Google will now publish new source code to the Android Open Source Project twice per year, down from releasing source code for every quarterly Android release
Google has announced that it will publish Android source code to AOSP in Q2 and Q4 of each year. — •
Context & Ripple Effects
This follows Google’s decision to [[a:883952|move Android development behind closed doors while retaining release-time source publication]]. Cutting AOSP publication from quarterly to Q2 and Q4 makes that boundary between internal development and public source delivery more pronounced.
The change also sits alongside Android’s shift toward risk-based security-update prioritization, though the reported source-code cadence does not itself establish a change in security-patch timing.
First-order effects
- OEMs, custom-ROM maintainers, and other AOSP downstream users will receive fewer official source drops, leaving longer intervals before they can inspect and integrate Google’s release code.
- Google gains a simpler public-release cadence while preserving AOSP publication twice yearly rather than at every quarterly Android release.
Second-order effects
- Device makers and independent Android builders may need to align platform-integration work to the two annual source windows or rely more heavily on their own branches between them.
- Less frequent public code availability can narrow the window for external review and upstream contribution, increasing the practical importance of Google’s internal development process.
Third-order effects
- If this cadence persists, Android’s open-source model may increasingly operate as periodic publication of a Google-led platform rather than a continuously synchronized development commons.
- The split between source delivery and security servicing could become more consequential: ecosystem participants will need to assess platform transparency and patch responsiveness as separate dimensions.
The trend: Android is moving toward more centrally governed platform development, with open-source publication becoming a scheduled downstream distribution mechanism.