On Tue, 17 Jan 2017 16:34:15 +0000
"Nashif, Anas" <email@example.com> wrote:
I see, apparently, we used a local release branch based on
v1.6.0-branch, that's why I saw "v1.6.0-27-gb6fb798" previously.
> I know git describe won’t work with this model, we need to find an
> alternative way. Probably when we change the version to 1.x.99, we
> could tag master so we can get something like: v1.6.99-1772-g003a46a
Yes, that would be nice. I'm just afraid that makes the release process
more and more complicated, but I guess as Zephyr grows, it would become
Thanks for the reply!