Skip to content

Commit

Permalink
Bump the version in master branch to 0.2.0
Browse files Browse the repository at this point in the history
  • Loading branch information
@jieyu
jieyu committed Dec 28, 2017
1 parent 9e88e4b commit 716f53e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion VERSION
View file
Original file line number Diff line number Diff line change
@@ -1 +1 @@
0.1.0
0.2.0

2 comments on commit 716f53e

@akutz
Copy link
Contributor

@akutz akutz commented on 716f53e Jan 31, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @jieyu,

I'm confused, why bump this version when 0.2.0 is not tagged yet? Shouldn't the master branch reflect the version of the previous, stable release? I've always used the VERSION file to reflect the version that git describe prints ahead of the number of commits since the previous, annotated tag. In this case that would still be 0.1.0...

@jieyu
Copy link
Member Author

@jieyu jieyu commented on 716f53e Jan 31, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@akutz that means that anything happens on the master branch after the 0.1.0 tag will be for the 0.2.0 release. This is the way I've been following in other projects. I don't have a strong opinion on that.

Please sign in to comment.