-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add roadmap, changelog, links #81
Conversation
CHANGELOG.md
Outdated
@@ -0,0 +1,25 @@ | |||
# 1.0.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this actually be 0.1.0? With semver, anything before 1.0 allows us to make breaking changes, and I'm more used to projects starting at 0.1.0 and graduating to 1.0 when they reach stability.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mimicked the version in Chart.yaml - 0.1.0 makes sense to me. Should we leave Chart.yaml as-is?
I'm going to add a TODO to our checklist to git tag
the master branch as 0.1.0
before release
ROADMAP.md
Outdated
* Job | ||
* CronJob | ||
* ReplicaSet | ||
* ReplicationController |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks great, but I'm not sure we want to commit to ReplicationController
as that seems to be a pretty outdated/unused resource at this point if I'm understanding it correctly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
No description provided.