Branch and release

Android code line

The android open-source project maintains a complete software heap obligation, and is transplanted by OEM and implemented by other devices (Translator's note: original words: implementors) and runs on the actual hardware. Therefore, we maintain a code line number to clearly separate the unstable experimental work of the current stable Android version.

The following chart depicts the level of concept for managing code and publishing in an aosp. We refer to these simple operations as "code lines" instead of "branches", because at any specific time, these may be more than one branch with a specific "code line ". For example, when a release is reduced, it will sometimes become a new branch in git. Sometimes it is not based on the time needed.

Notes and explanations

• OneReleaseCorresponding to the official version of an Android platform, such as 1.5 and 2.1. Generally, the release of a platform corresponds toSdkVersionThe domain is used in the androidmanifest. xml file and is defined inframeworks/base/api.

• OneUpstreamThe project is an open-source project that pulls code from the android stack. These include obvious projects, such as the Linux kernel and WebKit, but over time we migrated some semi-autonomous Android projects (such as Dalvik, Android SDK tool, bionic, etc) work as an "upstream" project. Generally, these projects are fully developed in the public tree. In some upstream projects, development directly contributes to the upstream projects. View the upstream project details. In both cases, snapshots are regularly pulled to the release.

• Charts refer to "eclair" and "Froyo"; however, they are simple placeholders, and charts actually reflect the overall release and branch strategy.

• At all times, a single release code line (which may include more than one branch in GIT) is considered as the only model source code for a specific Android platform version. OEMs and other group building devices will pull from only one release branch.

• We will set up "lab" code lines to capture changes from the community, so they can be iterated and have a stable eye.

• A stable change is finally pulled to a production branch. Note that Zhejiang only applies to bug fixes, application improvements, and other things that do not affect platform APIs.

• If necessary, the change will be pulled to the release branch from the upstream project (including android "upstream" project projects ).

• Version n + 1 (the main version of the next framework and platform API) will be developed by Google. See the following details.

• If necessary, the changes will be pulled, published, and lab branches from the upstream to the private branch of Google.

• When the platform API of the next version is stable and fully tested, Google will cut the release of the next platform version. (This is special. Refer to a new SdkVersion.) This will also correspond to the internal code lines produced by a public release Branch and the new current platform code lines.

• When a new platform version is removed, a corresponding experiment code line will be created at the same time.

Private code lines

The above source management strategy includes a code line that Google will keep private. The reason is to focus on the current public version of Android.

OEM and other devices build a device that is naturally equipped with the latest Android version. Similarly, application developers do not want to deal with more strictly required platform versions. At the same time, Google retains the responsibility of the android strategic direction as a platform and a product. Our approach is to protect the security of Android-related intellectual property rights based on the dominant features of the flagship device focusing on a small number.

As a result, Google frequently holds confidential information from third parties, and we must avoid disclosing sensitive feature units. We have mortgaged appropriate protection. At the same time, these are real risks. This platform has been generated from many platform versions that are currently present. For these reasons, we have constructed this open source program-including third-party contributions-focusing on the current public stable version of Android. The next version of "Deep Development" on this platform will take place privately until it has become officially released.

We acknowledge that many contributions will disagree with this approach. We respect others and may have a different opinion. However, we feel that this approach is the best and we have chosen to implement it.