
That sounds great thanks, and I agree about `major-fix` I was just out of
inspiration.
Any idea for the very first component? simply `release` maybe?
release/major/minor/patch
On 19 May 2015 at 19:19, Adam Bergmark
"major-fix" seems strange to me. I'd expect major to bump the 2nd component since it's part of the major version. Likewise the PVP uses "patch" for the 4th component.
On Tue, May 19, 2015 at 7:02 PM, Alois Cochard
wrote: Hi all,
I am currently writing a tool to automate the release and version bump of cabal projects.
Currently you can call the tool by giving as argument the rank of the branch you want to bump, for example given 0.0.0.0:
- `cabal-release 0` bump to `1` - `cabal-release 1` bump to `0.1` - `cabal-release 2` bump to `0.0.1` - `cabal-release 3` bump to `0.0.0.1`
As we are not all robots (yet), I thought that in addition to this it would be great if the user could give a human friendly name for the rank.
For now, here is what I have for the different rank: 0 == --major 1 == --major-fix 2 == --minor 3 == --minor-fix
I'm curious to know what you think of those names? any suggestions or known established convention about that?
Thanks
-- *Λ\ois* http://twitter.com/aloiscochard http://github.com/aloiscochard
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
-- *Λ\ois* http://twitter.com/aloiscochard http://github.com/aloiscochard