1# Perfetto UI Release Process 2 3The UI has three release channels which are configured by the 4[channels.json](/ui/release/channels.json) file. The channels are: 5 6- `stable`, the version served by default on ui.perfetto.dev. 7 Updated every four weeks. 8- `canary`, a less stable but fresher release. Updated every 1-2 weeks. 9- `autopush`, the current HEAD version of the UI. Unstable. 10 11The release process is based around a four week cycle. 12 13- Week 1: Update `canary` to `HEAD`. 14- Week 2: Update `canary` to `HEAD`. 15 Canary stabilization week 1/2 starts here. 16 Only critical bug fixes can be cherry-picked onto `canary`. 17- Week 3: Canary stabilization week 2/2. 18- Week 4: Update `stable` to current `canary`, update `canary` to `HEAD`. 19 20After the fourth week the cycle repeats from week one. 21This is so that: 22 23- Canary soaks for two weeks before being promoted to stable. 24- Newer features can be tried out in Canary within a week, or two at most (if 25 in the stabilization weeks). 26- Stable users aren't disrupted more than once per month. 27 28## Changing release channel 29 30NOTE: The channel setting is persistent across page reloads. 31 32The channel the UI is currently using is displayed in the top left corner. 33If the tag after the logo shows `autopush` or `canary` that is the current channel 34and if no tag is displayed the current channel is `stable`. 35 36 37 38To change the channel the UI is using between `stable` and `canary` you can use the toggle on the [entrance page](https://ui.perfetto.dev). 39 40 41 42To change to the `autopush` channel, open the `Flags` screen in the `Support` 43section of the sidebar, and choose `Autopush` in `Release channel`. 44 45## Which version am I using? 46 47You can see the version of the UI you are currently using in the bottom left hand corner of the UI. 48 49 50 51Clicking on the version number takes you to Github where you can see which commits are part of this version. The version number format is `v<maj>.<min>.<Commit SHA1 prefix>` where `<maj>.<min>` are extracted from the top entry in the 52[CHANGELOG](/CHANGELOG). 53 54## Cherry-picking a change 55 56If a change needs to be backported onto canary or stable branches, do the 57following: 58 59```bash 60git fetch origin 61git co -b ui-canary -t origin/ui-canary 62git cherry-pick -x $SHA1_OF_ORIGINAL_CL 63git cl upload 64 65# Repeat for origin/ui-stable branch if needed. 66``` 67 68Once the cherry-picks are landed, send out a CL to update the 69[channels.json](/ui/release/channels.json) in the `master` branch. See 70[r.android.com/1726101](https://r.android.com/1726101) for an example. 71 72```json 73{ 74 "channels": [ 75 { 76 "name": "stable", 77 "rev": "6dd6756ffbdff4f845c4db28e1fd5aed9ba77b56" 78 // ^ This should point to the HEAD of origin/ui-stable. 79 }, 80 { 81 "name": "canary", 82 "rev": "3e21f613f20779c04b0bcc937f2605b9b05556ad" 83 // ^ This should point to the HEAD of origin/ui-canary. 84 }, 85 { 86 "name": "autopush", 87 "rev": "HEAD" 88 // ^ Don't touch this one. 89 } 90 ] 91} 92``` 93 94The state of `channels.json` in the other branches is irrelevant, the release 95infrastructure only looks at the `master` branch to determine the pinning of 96each channel. 97 98After the `channels.json` CL lands, the build infrastructure will pick it up 99and update ui.perfetto.dev within ~30 mins. 100 101Googlers: You can check build progress and logs on 102[go/perfetto-ui-build-status](http://go/perfetto-ui-build-status). See also 103[go/perfetto-ui-autopush](http://go/perfetto-ui-autopush) and 104[go/perfetto-ui-channels](http://go/perfetto-ui-channels) for the design docs of 105the serving infrastructure. 106 107## Publishing the Perfetto Chrome extension 108Googlers: see go/perfetto-release-chrome-extension 109
