Hi Kevin,
On 7 Nov 2016, at 9:02, Kevin Townsend wrote:
I'm just migrating over to develop for mynewt-core and the newt tools
repos, and noticed the following after updating the command line tools
from develop:
- 'newt version' -> returns 0.9.0 in develop, this should probably be
0.10.0 to verify that you are using something different than the
master branch?
+1
- 'newtmgr version' -> doesn't exist. It might be useful to add this
as a sanity check of sorts when working with multiple branches and
versions?
+1
It's easy enough to send a pull request for these, but I wanted to
check if these two items are perhaps intentional and maybe the 0.10.0
version update only happens at release?
We don’t really have a policy here, which is why the newt version
hasn’t been updated. I think once we roll a release, we should always
update newt to the subsequent version, so that people can differentiate.
We might want to have some indicator that it is built off a
non-released version as well (maybe a build date?)
Sterling
