RJ
Different versions in rebar.config and app.src
I used following command:
rebar3 relflow -u "v2.0.1" -x "2.0.2"
it updated version in rebar.config to 2.0.2, generated correct v2.0.2 tag, but my app.src now has "20170224-154350-relflow" in vsn field instead of "2.0.2".
Is this a bug or I missed something in documentation?
a release can contain multiple apps.
the release version is separate from the app(s) versions.
the -u setting is changing the release version; the app versions are generated automatically by relflow, and there is no way to specify them on the command line.
so not a bug. make sense?
All my dependencies use semantic versioning. This causes that my app is the only one to have "strange version". Stdlib uses semantic versions for included applications. Changelogs with sematic versions are much easier to navigate and read. It is also harder to tell which version is loaded in the system, eg when using code:which/1. It is easier to remember Johnny fixed issue X in 2.1.2 than Johny fixed issue X in 20170226-023135-relflow, or was it 20170226-024135-relflow?.
It would make more sense for me if it worked the other way around. App - getting proper semantic version Release - getting date based version