Merge pull request #16 from tpiperatgod/main

Prepare for release v0.5.0

Author: benjaminhuo

CHANGELOG.md

@@ -0,0 +1,14 @@
+# 0.5.0
+
+> This is the first release of OpenFunction CLI
+
+`[CHANGE]`
+
+`[FEATURE]`
+
+- Add `install`, `uninstall` and `demo` subcommands
+
+`[ENHANCEMENT]`
+
+`[BUGFIX]`
+

RELEASE.md

@@ -0,0 +1,67 @@
+# Releases
+
+This page describes the release process and the currently planned schedule for upcoming releases as well as the respective release shepherd.
+
+## Release schedule
+
+| release series | date  (year-month-day) | release shepherd                            |
+|----------------|--------------------------------------------|---------------------------------------------|
+| v0.5.0          | 2021-12-21                           | Laminar (GitHub: @tpiperatgod) |
+
+# How to cut a new release
+
+> This guide is strongly based on the [Prometheus release instructions](https://github.com/prometheus/prometheus/blob/master/RELEASE.md).
+
+## Branch management and versioning strategy
+
+We use [Semantic Versioning](http://semver.org/).
+
+We maintain a separate branch for each minor release, named `release-<major>.<minor>`, e.g. `release-1.1`, `release-2.0`.
+
+The usual flow is to merge new features and changes into the main branch and to merge bug fixes into the latest release branch. Bug fixes are then merged into main from the latest release branch. The main branch should always contain all commits from the latest release branch.
+
+If a bug fix got accidentally merged into main, cherry-pick commits have to be created in the latest release branch, which then have to be merged back into main. Try to avoid that situation.
+
+Maintaining the release branches for older minor releases happens on a best effort basis.
+
+## Prepare your release
+
+For a new major or minor release, work from the `main` branch. For a patch release, work in the branch of the minor release you want to patch (e.g. `release-0.1` if you're releasing `v0.1.1`).
+
+Change the `Install the latest stable version` section in README.md to the new stable version:
+```bash
+kubectl apply -f https://github.com/OpenFunction/cli/releases/download/v<major>.<minor>.<patch>/bundle.yaml
+```
+
+Add an entry for the new version to the `CHANGELOG.md` file. Entries in the `CHANGELOG.md` are meant to be in this order:
+
+* `[CHANGE]`
+* `[FEATURE]`
+* `[ENHANCEMENT]`
+* `[BUGFIX]`
+
+Create a PR for the changes to be reviewed.
+
+## Publish the new release
+
+For new minor and major releases, create the `release-<major>.<minor>` branch starting at the PR merge commit.
+From now on, all work happens on the `release-<major>.<minor>` branch.
+
+Build the `ofn` cli:
+
+```bash
+make build
+```
+Tag the new release with a tag named `v<major>.<minor>.<patch>`, e.g. `v2.1.3`. Note the `v` prefix. You can do the tagging on the commandline:
+
+```bash
+tag="$(< VERSION)"
+git tag -a "${tag}" -m "${tag}"
+git push origin "${tag}"
+```
+Commit all the changes.
+
+Go to https://github.com/OpenFunction/cli/releases/new, associate the new release with the before pushed tag, paste in changes made to `CHANGELOG.md`, add cli file `ofn` and then click "Publish release".
+
+For patch releases, submit a pull request to merge back the release branch into the `main` branch.
+

pkg/components/inventory/shipwright.go

@@ -13,7 +13,7 @@ const (
 	ShipwrightVersionEnv                    = "SHIPWRIGHT_VERSION"
 	ShipwrightYamlEnv                       = "SHIPWRIGHT_YAML"
 	ShipwrightDefaultYamlFileTmpl           = "https://openfunction.sh1a.qingstor.com/shipwright/%s%s/release.yaml"
-	ShipwrightDefaultYamlFileTmplInRegionCN = "https://openfunction.sh1a.qingstor.com/shipwright/%s%s/release.yaml"
+	ShipwrightDefaultYamlFileTmplInRegionCN = "https://openfunction.sh1a.qingstor.com/shipwright/zh-%s%s/release.yaml"
 )
 
 type shipwright struct {