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.

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

Is it time to tag a new release? #23

Closed
thaJeztah opened this issue Apr 16, 2020 · 3 comments
Closed

Is it time to tag a new release? #23

thaJeztah opened this issue Apr 16, 2020 · 3 comments

Comments

@thaJeztah
Copy link
Member

I noticed this repository tagged a v1.0.0 release, but after that added a go.mod, and various other changes;

v1.0.0...cd3ce71

wondering if there's plans to tag a new release, or if other changes are still in the pipeline

(came here, because I noticed BuildKit is using a version from master, and because of that moby/moby as well)

@mxpv @estesp @crosbymichael @tonistiigi

@crosbymichael
Copy link
Member

we can tag if a commit makes sense. will this be a 1.1 or a 1.0.1?

@thaJeztah
Copy link
Member Author

I think I see some new functions were added, so I guess it would be 1.1.0 (minor should be updated for new features).

It's not super urgent (as in: if we know things are in the pipeline, feel free to wait for those)

@AkihiroSuda
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants