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

release 0.3.0 before breaking changes? #19

Closed
Quantisan opened this issue Apr 8, 2013 · 3 comments
Closed

release 0.3.0 before breaking changes? #19

Quantisan opened this issue Apr 8, 2013 · 3 comments

Comments

@Quantisan
Copy link
Collaborator

Incanter is dependent on 0.3.0-SNAPSHOT. Can we release 0.3.0 before api breaking changes are applied please?

@mikera
Copy link
Collaborator

mikera commented Apr 8, 2013

Sounds sensible. Though why is Incanter depending on SNAPSHOT releases? That's not a good idea in general

Even better might be to adopt a git-flow type system where:

  • master always contains the latest released version x.y.z
  • develop branch is used for development of next full release x.(inc y).0-SNAPSHOT
  • hotfix, feature and release branches used on an as-needed basis.

See: http://nvie.com/posts/a-successful-git-branching-model/

@ejackson
Copy link
Collaborator

ejackson commented Apr 9, 2013

Oooh, I didn't know this. Yikes - I assumed it was 0.2. Is Incanter passing with the current HEAD ?

@Quantisan
Copy link
Collaborator Author

Sorry, it seems that I made it use a release and forgot about it myself... Apologies for the false alarm!

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