{"id":153445,"date":"2026-01-07T11:11:58","date_gmt":"2026-01-07T09:11:58","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/google-perehodit-k-publikaczii-koda-android-dvazhdy-v-god"},"modified":"2026-01-07T11:11:58","modified_gmt":"2026-01-07T09:11:58","slug":"google-perehodit-k-publikaczii-koda-android-dvazhdy-v-god","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/google-perehodit-k-publikaczii-koda-android-dvazhdy-v-god","title":{"rendered":"Google is shifting to publishing the Android code twice a year.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
A warning about a change in the code publication scheme has appeared on the AOSP (Android Open Source Project) repository website, where the source code of the Android platform is hosted. Going forward, new Android code will only be released after each subsequent release. AOSP content will now be updated only twice a year \u2014 in the second and fourth quarters. Previously, Google practiced quarterly code releases. <\/p>\n
Instead of the continuously updated branch 'aosp-main' for building and developing changes, it is recommended to use the new branch 'android-latest-release', which is associated with the state of the codebase of the latest Android release (currently, it is 'android16-qpr2-release'). This change will not affect the monthly publication of patches addressing vulnerabilities, which will continue to be released in the 'android-security' branches. <\/p>\n
The reasons for this change include the desire to ensure platform stability for the Android ecosystem and to align AOSP with a trunk-stable development model, which will simplify Android development, eliminate the need to maintain multiple branches, and provide third-party developers with more stable and secure code. Having separate internal and public branches led to increasing discrepancies during release development, requiring resources to synchronize changes and merge patches between different branches. <\/p>\n
Last year, Google limited the submission of device-specific changes for Pixel to AOSP and moved to develop releases behind closed doors without publishing intermediate results in AOSP. Prior to this, the platform had been developed using a mixed development model, where some components of Android, such as the Bluetooth stack, build system, update engine, and virtualization framework, were developed publicly, while others were initially created in an internal repository and revealed after release. According to the new model, only an internal branch is used for development, and code from it is transferred to the AOSP repository in connection with releases. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"