Lines Matching +full:curl +full:- +full:for +full:- +full:win
5 Before snapshotting a release, check that no [release-blockers](http://b/savedsearches/5776355) are
15 Next, decide the version number for the new release (vX.Y).
17 The minor version number is incremented only for minor changes / fixes on top of the monthly
18 release (cherry-picks on the releases/vN.x branch).
25 [LUCI](https://luci-scheduler.appspot.com/jobs/perfetto) by triggering all the
26 builds and waiting for their success. If any of the builds fail, fix the failure
34 running `perfetto --version` should show your new version number.
38 Create a release branch for the new major version ("v16.x" here):
44 git checkout -b releases/v16.x -t origin/releases/v16.x
47 Continue with [building the release](#building-and-tagging-the-release).
52 revision for the new release, resolving any conflicts you may encounter.
55 git checkout -b releases/v16.x -t origin/releases/v16.x
59 cherry-picking them individually:
62 git cherry-pick <sha1>
71 Update the CHANGELOG with a dedicated entry for the new minor version.
77 For an example see [r.android.com/1730332](https://r.android.com/1730332)
80 v16.1 - 2021-06-08:
82 * Cherry-pick of r.android.com/1716718 which missed the v16 branch ... .
85 v16.0 - 2021-06-01:
94 tools/gen_amalgamated --output sdk/perfetto
96 git commit -m "Amalgamated source for vX.Y"
103 cmake -B build
104 cmake --build build
107 3. Upload the new release for review.
110 git cl upload --no-squash --bypass-hooks -o banned-words~skip
113 If you get an error about a missing Change-Id field (`remote: ERROR: commit
114 a7c7c4c: missing Change-Id in message footer`), install the commit-msg hook
118 curl -Lo .git/hooks/commit-msg http://android-review.googlesource.com/tools/hooks/commit-msg
119 chmod u+x .git/hooks/commit-msg
120 git commit --amend
123 4. Once the release has been reviewed and landed, create and push the tag for
134 git tag -a -m "Perfetto vX.Y" vX.Y
140 - [docs/instrumentation/tracing-sdk.md](/docs/instrumentation/tracing-sdk.md)
141 - [examples/sdk/README.md](/examples/sdk/README.md)
143 6. Send an email with the CHANGELOG to perfetto-dev@ (internal) and to the
144 [public perfetto-dev](https://groups.google.com/forum/#!forum/perfetto-dev).
149 on https://luci-scheduler.appspot.com/jobs/perfetto . Wait for all the bots
152 8. Run `tools/package-prebuilts-for-github-release vX.Y`. It will pull the
153 prebuilts under `/tmp/perfetto-prebuilts-vX.Y`.
154 - There must be 10 zips in total: linux-{arm,arm64,amd64},
155 android-{arm,arm64,x86,x64}, mac-{amd64,arm64}, win-amd64.
156 - If one or more are missing it means that one of the LUCI bots failed,
158 - If this happens you'll need to respin a vX.(Y+1) release with the fix
162 - Select "Choose Tag" -> vX.Y
163 - "Release title" -> "Perfetto vX.Y"
164 - "Describe release" -> Copy the CHANGELOG, wrapping it in triple backticks.
165 - "Attach binaries" -> Attach the ten .zip files from the previous step.
167 10. Run `tools/roll-prebuilts vX.Y`. It will update the SHA256 into the various