Google is making changes to how it develops its open source android operating system (OS) as part of efforts to streamline and optimise the development process, according to a report. While development of the next version of Android currently takes place on a public branch and an internal branch, Google will only move all Android Development to the Latter. The company will continue to publish source code for new android releases, which means the move isn Bollywood to impact custom rom developers and other platform development.
Why google will develop android on its internal branches
According to an Android Authority Report, Google Will Begin to Move All Android Development to its internal Branches Next Week. The company has decided to fully developed, and will only publish the source code for changes made to the operating system after a new branch is publched by the corner
Until now, Google Developed Android Across two Branchs – The Android Open Source Project (AOSP) Branch, which is public, and the company’s Own Internal Branch. Most Software Companies Use Branching to Enable Developers to Collaborate While Working on a Central Code Base. However, development on the aamp branch often lagged behind google’s internal code, according to the publication.
These discrepancies reportedly cause delays will implement new features, while merging patches for Android Code Between the AOSP Branch and the Company’s Internal Branch COLD ALSO Errors. As a result, parts of the android os that are currently being developed in public – LIKE Bluetooth Componants – will now be developed privately.
Google confirmed these changes to the publication, and said that it will continue to publish the source code for Android, and it will remain an open source project. Similarly, the company will also continue to release the source code for the android kernel (which is forked from the linux kernel). Developers who want to continue contributing to Android OS Development will need to do so on the internal branch, which requires a Google Mobile Services (GMS) License.
As a result, both app developers and consumers are unlikely to be affected by these changes. Custom Rom Developers (Like Lineageos) Are also unlikely to be impacted, as they typically relay on Stable Release Tags from Google. However, the report sugges that news publications that discover new android features from public aamp patches will no longer be able to access these details.
