|
1 | 1 | # Release Process |
2 | 2 |
|
3 | | -## Change milestone |
4 | | - - Change milestone applier so new changes can be applied to the appropriate release |
| 3 | +## Change milestone |
| 4 | + - Change milestone applier so new changes can be applied to the appropriate release |
5 | 5 | - Open a PR in https://github.com/kubernetes/test-infra to change this [line](https://github.com/kubernetes/test-infra/blob/25db54eb9d52e08c16b3601726d8f154f8741025/config/prow/plugins.yaml#L344) |
6 | 6 | - Example PR: https://github.com/kubernetes/test-infra/pull/16827 |
7 | 7 |
|
|
10 | 10 | - Fast-forward the release branch to the selected commit. Always release from the release branch and not from master! |
11 | 11 | - `git fetch upstream` |
12 | 12 | - `git merge --ff-only upstream/master` |
13 | | - - Create tag with git |
| 13 | + - Create tag with git |
14 | 14 | - `export RELEASE_TAG=v0.4.6` (the tag of the release to be cut) |
15 | 15 | - `git tag -s ${RELEASE_TAG} -m "${RELEASE_TAG}"` |
16 | 16 | - -s creates a signed tag, you must have a GPG key [added to your GitHub account](https://docs.github.com/en/enterprise/2.16/user/github/authenticating-to-github/generating-a-new-gpg-key) |
17 | 17 | - `git push upstream ${RELEASE_TAG}` |
18 | | - - `make release` from repo, this will create the release artifacts in the `out/` folder |
| 18 | + - Update the file `metadata.yaml` if is a major or minor release |
| 19 | + - `make release` from repo, this will create the release artifacts in the `out/` folder |
19 | 20 | - To install the `release-notes` tool, see https://github.com/kubernetes/release/blob/master/cmd/release-notes/README.md |
20 | 21 | - Export GITHUB_TOKEN |
21 | 22 | - Run the release-notes tool with the appropriate commits. Commits range from the first commit after the previous release to the new release commit. |
22 | 23 | ``` |
23 | | - release-notes --github-org kubernetes-sigs --github-repo cluster-api-provider-azure \ |
| 24 | + release-notes --github-org kubernetes-sigs --github-repo cluster-api-provider-azure \ |
24 | 25 | --start-sha 1cf1ec4a1effd9340fe7370ab45b173a4979dc8f \ |
25 | | - --end-sha e843409f896981185ca31d6b4a4c939f27d975de |
| 26 | + --end-sha e843409f896981185ca31d6b4a4c939f27d975de |
26 | 27 | ``` |
27 | 28 | - Manually format and categorize the release notes |
28 | 29 |
|
29 | | -## Promote image to prod repo |
| 30 | +## Promote image to prod repo |
30 | 31 | Promote image |
31 | 32 | - Images are built by the [post push images job](https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api-provider-azure#post-cluster-api-provider-azure-push-images) |
32 | 33 | - Create a PR in https://github.com/kubernetes/k8s.io to add the image and tag |
33 | 34 | - Example PR: https://github.com/kubernetes/k8s.io/pull/1030/files |
34 | 35 | - Location of image: https://console.cloud.google.com/gcr/images/s-staging-cluster-api-azure/GLOBAL/cluster-api-azure-controller?rImageListsize=30 |
35 | 36 |
|
36 | | -## Release in GitHub |
| 37 | +## Release in GitHub |
37 | 38 | Create the GitHub release in the UI |
38 | 39 | - Create a draft release in GitHub and associate it with the tag that was created |
39 | 40 | - Copy paste the release notes |
|
45 | 46 |
|
46 | 47 | cluster-api-provider-azure follows the [semantic versionining][semver] specification. |
47 | 48 |
|
48 | | -As of this writing, we have not produced as a major or minor release. |
| 49 | +As of this writing, we have not produced as a major or minor release. |
49 | 50 |
|
50 | 51 | Current pre-release versions can be expected to have breaking changes as we move towards declaring a public API version. |
51 | 52 |
|
|
0 commit comments