Skip to content
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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

v0.3.0 (or v0.2.1) release 馃懠 #16

Closed
vdemeester opened this issue Jul 2, 2016 · 4 comments
Closed

v0.3.0 (or v0.2.1) release 馃懠 #16

vdemeester opened this issue Jul 2, 2016 · 4 comments
Labels
kind/question

Comments

@vdemeester
Copy link
Collaborator

vdemeester commented Jul 2, 2016 •
edited
Loading

We should tag the v0.3.0 (or v0.2.1) release (and update vendoring in docker/docker)

/ping @calavera @thaJeztah @icecrime @dnephin
@thaJeztah
Copy link
Member

Guess it depends on the changes; if only bug fixes, then 0.2.1, otherwise 0.3;
v0.2.0...master

@dnephin
Copy link
Contributor

dnephin commented Jul 3, 2016

0.2.1 sounds appropriate, I think these are basically just bug fixes.

@thaJeztah
Copy link
Member

SGTM

@vdemeester
Copy link
Collaborator Author

Ok good, I pushed a v0.2.1 tag. I'll update hack/vendor.sh of docker/docker soon then 馃懠

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vdemeester @dnephin @thaJeztah