Skip to content

release strategy for logcheck #312

@pohly

Description

@pohly

/kind feature

Right now, logcheck doesn't get released "properly" (no tag, no release notes). Kubernetes imports it via the commit hash (https://github.com/kubernetes/kubernetes/blob/0ade4678a7ba527d22f6baa81034dea423267608/hack/tools/go.mod#L14).

We could:

  • tag it with hack/tools/v0.1.0
  • move it to a separate repo
  • do nothing and keep importing it via hash

Describe the solution you'd like

According to the discussion in kubernetes/kubernetes#108725 (comment), a separate repo seems more appropriate. There is no technical reason why the tool is in klog and releases are easier when it is a stand-alone repo.

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions