> On Nov 7, 2016, at 6:15 AM, Sterling Hughes <[email protected]> wrote: > > 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
I filed a bug on this in Jira a week or so ago. > >> - '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 +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?) I'd like to see the 'develop' branch get a version-string of the next version to be released. So since 0.9.0 is the master branch, the develop branch should have 1.0.0-dev maybe? dg -- David G. Simmons (919) 534-5099 Web <https://davidgs.com/> • Blog <https://davidgs.com/davidgs_blog> • Linkedin <http://linkedin.com/in/davidgsimmons> • Twitter <http://twitter.com/TechEvangelist1> • GitHub <http://github.com/davidgs> /** Message digitally signed for security and authenticity. * If you cannot read the PGP.sig attachment, please go to * http://www.gnupg.com/ <http://www.gnupg.com/> Secure your email!!! * Public key available at keyserver.pgp.com <http://keyserver.pgp.com/> **/ ♺ This email uses 100% recycled electrons. Don't blow it by printing! There are only 2 hard things in computer science: Cache invalidation, naming things, and off-by-one errors.
