Prepare stable release #29
Conversation
CHANGELOG.md
Outdated
There was a problem hiding this comment.
i think we should actually not clutter the changelog with this. users of the library do not see any effect of that change, its only used when installing the lib for development.
There was a problem hiding this comment.
Not to mention I have to revert it because integration tests are using puli which is beta 😄
sagikazarmark
force-pushed
the
stable_release
branch
2 times, most recently
from
c60ba77 to
5056c3b
Compare
There was a problem hiding this comment.
I would use 1.0-dev here. The reason is that commits after the first stable release will probably be bug fixes. So the following release will rather be 1.0.1 and not 1.1.0. The branch alias can then be updated when the first new feature was merged (which requires to bump the minor version).
There was a problem hiding this comment.
Well, @dbu came with the same reason. I thought otherwise so far, but this is not something which I cared about too much, so probably you are right.
There was a problem hiding this comment.
Thank you @sagikazarmark for merging them all. :)
There was a problem hiding this comment.
thinking about this again, i think the main argument for calling this 1.0 is that people can get their fixes by depending on 1.0.*@dev and play it safe with not ending up with new features of 1.1 that might have side effects for them.
No description provided.