Release v0.2.0

[AvineshTripathi]

Version: v0.2.0
Candidate for release: df24a641e

changelog:

df24a64 cleanup: doc updates on getting-started guide. (#135)
7215277 docs: document NoExecute taint risks and add admission warning (#120)
16dac86 docs: add example for security agent readiness (#101)
dae1ba2 Version bump for devcontainer and golangci-kal (#132)
996937a feat(config): add webhook as kustomize component (#122)
6e6329d cleanup: Remove unused globalDryRun feature (#123) (#130)
0715ec6 enhancement: Dockerfiles and Go Mod version (#113)
67fb858 fix(dev-container): disable moby in newer version of debian (#127)
2d4788f docs: remove stale docs/spec.md (#126)
354b151 fix: add missing boilerplate headers in metrics.go (#119)
f330572 docs: updatingTEST_readme.md (#118)
243aa89 update cni readiness example to use daemonset for reporter (#116)
13a3729 refactor: enable metrics manifests (#79)
5c179b9 fix(README): update path to logo (#115)
21d133a add video demo (#114)
2579247 feat: add a pull request template (#110)
f579d82 Mark controller as system-cluster-critical to prevent eviction (#108)
9dbc9b3 update logo for heptagon shape (#109)
13aed94 use status.patch api for node updates (#104)
dc4a0b1 doc: managing cni-readiness with node-readiness-controller (#99)
dfe24ec update cni-patcher to use registry.k8s image (#96)
8377f39 build-installer to create crd and install manifests (#95)
09bcfa3 Doc install (#92)
86e143d update reference example build-installer make target (#93)
d2abc01 v0.1.1: add release notes (#91)

Task list from Release process -

• Propose the release

• Prepare the release branch

• Tag the release

• Create the Github Release

• Post Release Tasks

  • Announcement to dl/sig-node

  • [ ] Announcement to dl/k8s-dev

[ajaysundark]

Thanks for kickstarting this, @AvineshTripathi. Should we manage this as a patch release targeting version v0.2.0 instead?
We discussed and went with v0.1.1 last time, as it was cherrypick on top of v0.1.0 for missing fixes.

@Priyankasaggu11929 wdyt?

[Priyankasaggu11929]

Should we manage this as a patch release targeting version v0.2.0 instead?

Oh yes, it should be v0.2.0.
Basically we are aiming to do a new minor version release now - so a matching release branch - release-v0.2

Not a new patch release on the existing minor version tag - v0.1.0 (v0.1.2 will be a patch version).

(I totally misread the proposed tag earlier. )

[ajaysundark]

so a matching release branch - release-v0.2

I propose we maintain semver format and use branch naming convention release-v0.2.0

lgtm to proceed with the release.

[ajaysundark]

The new release automation (#144) also submitted the first VERSION metadata, and created the release branch and tag , but this moved the milestone for a different commit -- 6c3c15d

[ajaysundark]

Thanks for driving this release @AvineshTripathi!

/close

[k8s-ci-robot]

@ajaysundark: Closing this issue.

Details

In response to this:

Thanks for driving this release @AvineshTripathi!

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.