Re: git describe of v1.5.0-3830-gecd209f


Paul Sokolovsky
 

Hello Anas,

On Tue, 17 Jan 2017 16:34:15 +0000
"Nashif, Anas" <anas.nashif(a)intel.com> wrote:

Current "git describe" for the master gives "v1.5.0-3830-gecd209f".
This is a little bit unfortunate, especially that soon after 1.6.0
it was like "v1.6.0-27-gb6fb798". I assume there were good thinking
on switching from "tag major releases in the master" to "tag any
release in a branch", so this is just a late notice of when it may
matter.
[]


The 1.6 tag was created on the branch. Starting with 1.6 we create a
branch during the stabilisation period and continue development on
master or the next release. This is the current model also described
on the wiki.
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
such anyway.

Anas
Thanks for the reply!

--
Best Regards,
Paul

Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

Join devel@lists.zephyrproject.org to automatically receive all group messages.