On the repository website AOSP (Android Open Source Project), a recent warning has been issued regarding a change in the code publishing process. Moving forward, new Android code will only be opened after the next release, with updates to AOSP content now scheduled for the second and fourth quarters of the year. This marks a shift from the previous practice of quarterly code publications by Google.
Instead of the continuously updated branch “aosp-main“, developers are advised to utilize the new branch “android-latest-release“. This branch, identified by the code base of the latest Android release (such as the current “android16-qpr2-release”), is recommended for creating builds and implementing changes. However, regular patches addressing vulnerabilities will continue to be posted on a monthly basis in the “android-security” thread.
The rationale behind this change is to ensure platform stability within the Android ecosystem and transition AOSP to a trunk-stable development model. This shift aims to streamline Android development, remove the need for managing multiple branches, and provide third-party developers with a more stable and secure code base. Previously, maintaining separate internal and public branches led to discrepancies accumulating as releases progressed, necessitating resources for synchronizing and merging changes between different branches.
Notably, Google had recently restricted the submission of Pixel-specific changes to AOSP and opted for developing releases privately without disclosing intermediate progress on AOSP. Before this adjustment, the platform followed a mixed development model where certain components like the Bluetooth stack, build system, update engine, and virtualization framework were developed publicly, while others were initially created in an internal repository and unveiled post-release. Under the new model, a solitary internal branch is employed during development, with code being transferred to the AOSP repository in conjunction with releases.