diff options
| author | Chris Wailes <chriswailes@google.com> | 2023-11-29 15:51:29 -0800 |
|---|---|---|
| committer | Chris Wailes <chriswailes@google.com> | 2024-04-17 16:53:49 +0000 |
| commit | 2c0a43ffb6e5243c1a4a4b25d3b6330701914cdc (patch) | |
| tree | a5340d3bb4e633b9ab6b38174c7203f01ebaf41f | |
| parent | b1eece0d01df4d10e0a15f3c4206e93075bea34d (diff) | |
| download | android_rust-2c0a43ffb6e5243c1a4a4b25d3b6330701914cdc.tar.gz | |
Update README with new cleanup instructions
Test: N/A
Change-Id: I3dc756f0ef2049660b850c77ff26ca1dd7e1df5f
| -rw-r--r-- | README.md | 48 |
1 files changed, 11 insertions, 37 deletions
@@ -41,10 +41,10 @@ purpose of providing prebuilts for other developers. ### Section 1.0 Prebuilds Prep -Decide on what prebuilt is being deleted during this release cycle. We like to -keep three in hand (see -[policy](https://g3doc.corp.google.com/company/teams/android_native_tools_and_libraries/RustToolchainPolicy.md?cl=head)). -The available versions are in prebuilts/rust/linux-x86/ +When beginning the update process there should only be a single prebuilt +version checked in. If this is not the case then it is likely that a downstream +team is stuck on a previous version. Check to see if the client teams have +completed their migration and, if so, begin deleting the unused prebuilts. Post on Buganizer ticket that the release process is beginning, asks for patches, and declares the prebuilt that will be deleted. @@ -324,13 +324,12 @@ version number, e.g. `rust-update-prebuilts-1.59.0`. #### Step Release-11: Remove previous prebuilts -If the new release is a point or patch release (e.g. 1.60.1/1.60.1.p1) you may -skip this step. - -If this is a new minor release (e.g. 1.61.0) then start by inspecting the -preceding release. If it contains any point or patch release delete all but the -last one. This can be done either in one large CL or in individual CLs, though -the latter is preferred. +Our goal is to keep only a single prebuilt checked out under steady-state +conditions. Once a new release has been stabilized we can delete any previous +versions of the toolchain that are not actively being used by a downstream team. +In this case "stabilized" means that each client team that is actively working +on updating to the newest version has completed their work and is happy with the +state of the new prebuilt. A release can be removed using the following commands: @@ -355,35 +354,10 @@ Prebuilts before version 1.61.0.p1 will not include `linux-musl-x86` binaries so it will be necessary to remove that target from the above command until 1.60.0 is removed. -After the preceding release is cleaned up remove older releases until only the -new release and two preceding release remain. We keep three on hand. - If a team is depending on the prebuilt you plan to delete you can pin their code. -#### Step Release-12: Tagging (Publish Compiler Prebuilt) - -Once the CL containing the new prebuilts has been merged it needs to be tagged. -This tag is not used by Android, but Chrome is using it to produce an MPM of our -compiler releases for their work. - -These commands do not have a review step like uploading a change, so be sure -that you have landed (not just uploaded) the commits from the previous step. - -```shell -$ cd prebuilts/rust -$ git tag rustc-$RUST_VERSION -$ git push aosp rustc-$RUST_VERSION -``` - -The new compiler will now be automatically made available to Chrome. (Actually -rolling the version of the compiler they're using is up to them, you don't need -to worry about that part.) - -You can check for tags -[here](https://android-review.googlesource.com/admin/repos/platform%252Fprebuilts%252Frust,tags/q/filter:1.61). - -#### Step Release-13: Wrapping it up +#### Step Release-12: Wrapping it up Create a ticket for the next release and assign it to the next team member. Check that the CC’s and hotlist (android_rust_toolchain) on it are consistent |