aboutsummaryrefslogtreecommitdiff
path: root/en/setup/build-numbers.html
diff options
context:
space:
mode:
Diffstat (limited to 'en/setup/build-numbers.html')
-rw-r--r--en/setup/build-numbers.html3
1 files changed, 2 insertions, 1 deletions
diff --git a/en/setup/build-numbers.html b/en/setup/build-numbers.html
index f0ba4a2e..10f50cd5 100644
--- a/en/setup/build-numbers.html
+++ b/en/setup/build-numbers.html
@@ -171,12 +171,13 @@ API levels and NDK releases provided for convenience:</p>
</tr>
</tbody>
</table>
-<p>Starting with Oreo, individual builds are identified with a new build ID format, in the form of PVBB.YYMMDD.bbb.</p>
+<p>Starting with Oreo, individual builds are identified with a new build ID format, in the form of PVBB.YYMMDD.bbb[.Cn].</p>
<p>The P part represents the first letter of the code name of the platform release, e.g. O is Oreo.</p>
<p>The V part represents a supported vertical. By convention, 'P' represents the primary platform branch.</p>
<p>The BB part represents a alpha numeric code which allows Google to identify the exact code branch that the build was made from.</p>
<p>The YYMMDD part identifies the date when the release is branched from or synced with the development branch. It is not guaranteed to be the exact date at which a build was made, and it is common that minor variations added to an existing build re-use the same date code as that existing build.</p>
<p>The bbb part identifies individual versions related to the same date code, sequentially starting with 001.</p>
+<p>An optional, alphanumeric Cn part identifies a hotfix on top of an existing PVBB.YYMMDD.bbb build, starting from A1.</p>
<p>Older Android releases from Cupcake to Nougat uses a different build ID scheme. These Android builds are identified with a short build code, e.g. FRF85B.
</p>
<p>The first letter is the code name of the release family, e.g. F is