To balance AOSP’s open nature with its product development strategy, Google maintains two primary Android branches: the public AOSP branch and its internal development branch. The AOSP branch is accessible to anyone, while Google’s internal branch is restricted to companies with a Google Mobile Services (GMS) licensing agreement.
为了平衡 AOSP 的开放性质与产品开发策略，Google 维护了两个主要的 Android 分支：公共的 AOSP 分支和其内部开发分支。AOSP 分支对任何人都开放，而 Google 的内部分支仅限于签署了 Google Mobile Services（GMS）许可协议的公司。
While some OS components, such as Android’s Bluetooth stack, are developed publicly in the AOSP branch, most components, including the core Android OS framework, are developed privately within Google’s internal branch. Google confirmed to Android Authority that it will soon shift all Android OS development to its internal branch, a change intended to streamline its development process.
而像 Android 的蓝牙堆栈这样的 OS 组件是在 AOSP 分支中公开开发的，但大多数组件，包括核心 Android OS 框架，都是在 Google 的内部分支中私下开发的。Google 已经确认将把所有 Android OS 的开发转移到其内部分支，这一改变旨在简化其开发流程。
...
Google confirmed to Android Authority that it is committed to publishing Android’s source code, so this change doesn’t mean that Android is becoming closed-source. The company will continue to publish the source code for new Android releases, so when Google releases Android 16 later this year, we’ll get the source code for the update. In addition, Google will continue to publish the source code for Android’s Linux kernel fork, as it is licensed under GPLv2, which mandates source code releases, and is separate from AOSP.
谷歌向 Android Authority 证实，它致力于发布 Android 的源代码，因此这一变化并不意味着 Android 将变成闭源。该公司将继续发布新 Android 版本的源代码，所以当谷歌在今年晚些时候发布 Android 16 时，我们将获得更新的源代码。此外，谷歌将继续发布 Android 的 Linux 内核分支的源代码，因为该内核是根据 GPLv2 许可发布的，必须发布源代码，并且与 AOSP 分开。
