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

released? #3

Closed
jasonkarns opened this issue Feb 15, 2016 · 2 comments
Closed

released? #3

jasonkarns opened this issue Feb 15, 2016 · 2 comments

Comments

@jasonkarns
Copy link
Contributor

Is this considered a 1.0.0 release? Could we get some git tags for releases? (even if not v1.0.0)

(And I strongly recommend the vX.Y.Z form for the tags for reasons)

@ztombol
Copy link
Owner

ztombol commented Feb 16, 2016

The libraries will follow semantic versioning so version numbers will be of the form vX.Y.Z. In the initial development phase, the major number will be kept 0 and the minor will be bumped on every release. In other words v0.Y.Z. I want to release v1.0.0 after we decided that we reached a certain level of stability.

I didn't want to create a tagged release right after publishing as I thought there would be a fair bit of changes once people could easily try out these libraries (i.e. not in a Bats pull request). Leaving it just a git version would suggest that we don't have a stable API yet.

In hindsight, it doesn't really matter and I could have tagged v0.1.0 right away. :)

I will tag v0.1.0 in bats-assert and bats-core as soon as I fix #6. So that the package manager support can progress.

_Edit:_ Changed #5 to #6. -- 2016-02-16 21:43 UTC

@ztombol
Copy link
Owner

ztombol commented Feb 16, 2016

@jasonkarns I tagged v0.1.0 in bats-core and bats-assert.

@ztombol ztombol closed this as completed Feb 16, 2016
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

2 participants