Skip to content
This repository has been archived by the owner on Sep 24, 2021. It is now read-only.

Figure out release strategy #67

Closed
chuckha opened this issue Jul 5, 2019 · 1 comment · Fixed by #95 or #114
Closed

Figure out release strategy #67

chuckha opened this issue Jul 5, 2019 · 1 comment · Fixed by #95 or #114
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.

Comments

@chuckha
Copy link
Contributor

chuckha commented Jul 5, 2019

/kind feature

Describe the solution you'd like
Right now we're using latest and building from HEAD. This is a very bad practice and we should figure out releases for this project.

I'm hoping that the GitHub packing is available now to solve a large part of this issue for us.

Anything else you would like to add:
Don't use latest image tag.

Environment:

  • Cluster-api-provider-docker version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@chuckha
Copy link
Contributor Author

chuckha commented Jul 22, 2019

  • Release a v0.1
  • Track cluster-api v1alpha1 on our release-0.1 branch (used for integration tests elsewhere)

/assign
/lifecycle active

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor.
Projects
None yet
2 participants