Merge pull request fluxcd#41 from fluxcd/release-v0.0.1-alpha.2

CHANGELOG.md

@@ -2,6 +2,23 @@
 
 All notable changes to this project are documented in this file.
 
+## 0.0.1-alpha.2 (2020-04-24)
+
+This is the second alpha release of source controller.
+
+It introduces a timeout field to the [`GitRepositoriesSpec`](docs/spec/v1alpha1/gitrepositories.md)
+and [`SyncAt` annotation to the common spec](docs/spec/v1alpha1/common.md#source-synchronization).
+Furthermore, it allows configuring the amount of concurrent reconciliation
+operations per reconciler using the newly introduced `--concurrent` flag
+(defaults to `2`), and introduces a `--log-json` flag to enable JSON logging.
+
+Liveness and readiness probes have been added to the deployment manifest, and
+the security has been strengthened by running the controller as a non-root user
+by default and adding a container security context. 
+
+Tests have been added to ensure correct behaviour of the `HelmChartReconciler`
+and `HelmRepositoryReconciler`.
+
 ## 0.0.1-alpha.1 (2020-04-16)
 
 This is the first alpha release of source controller.

config/manager/kustomization.yaml

@@ -6,4 +6,4 @@ resources:
 images:
 - name: fluxcd/source-controller
   newName: fluxcd/source-controller
-  newTag: v0.0.1-alpha.1
+  newTag: v0.0.1-alpha.2

docs/internal/release.md

@@ -0,0 +1,13 @@
+# Release
+
+To release a new version the following steps should be followed:
+
+1. Create a new branch from `master` i.e. `release-<next semver>`. This
+   will function as your release preparation branch.
+1. Add an entry to the `CHANGELOG.md` for the new release and change the
+   `newTag` value in ` config/manager/kustomization.yaml` to that of the
+   semver release you are going to make. Commit and push your changes.
+1. Create a PR for your release branch and get it merged into `master`.
+1. Create a `<next semver>` tag for the merge commit in `master` and
+   push it to remote.
+1. Confirm CI builds and releases the newly tagged version.