Hi Sterling,
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
I submitted a pull request ticking this up on (super trivial but at
least it's easy to integrate). I'm not sure if NewtBlinkyTag is
correct, though? Feel free to edit or reject if so:
https://github.com/apache/incubator-mynewt-newt/pull/25
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?)
If the version fields have to be integer values then perhaps in
'develop' releases you can insert the 32-bit unix epoch timestamp as the
last field? It isn't very human readable, but it does at least indicate
a clear difference between updates. It seems like this would fit:
struct image_version {
uint8_t iv_major;
uint8_t iv_minor;
uint16_t iv_revision;
uint32_t iv_build_num;
};
That said, it isn't a very elegant solution.
Another alternative might be a magic number that is converted to '-dev'
when detected. You can convert '-dev' to it's char equivalent in
uint32_t, for example, since it's 4 bytes wide.
