2.6 Release announcement

Lei YU mine260309 at gmail.com
Mon Feb 18 19:53:29 AEDT 2019


It turns out that 2.6.0 tag is on `thud` branch instead of master:

    $ git branch -a --contains tags/2.6.0
      remotes/origin/thud

Hopefully, we could fix this.

On Mon, Feb 18, 2019 at 4:48 PM Lei YU <mine260309 at gmail.com> wrote:
>
> Hi Brad, Kurt,
>
> The 2.6.0 tag is a bit weird, that `git describe` does not correctly get the
> latest tag:
>
>     $ git describe
>     2.6.0-rc1-242-g073a600a0
>
> This results in `/etc/os-release` to report the build is not from the 2.6.0
> tag but from 2.6.0-rc1.
>
> Some investigations:
>
> * Both `git describe --tags` and `git describe --abbrev=0 --tags` shows the
> latest tag is `2.6.0-rc1`:
>
>     $ git describe --tags
>     2.6.0-rc1-242-g073a600a0
>     $ git describe --abbrev=0 --tags
>     2.6.0-rc1
>
> * The only way to get the latest tag is with below command:
>
>     $ git describe --tags $(git rev-list --tags --max-count=1)
>     2.6.0
>
> * It indicates that the tag 2.6.0 is not on the master branch.
>
>     $ git branch --contains tags/2.6.0
>
>     $ git branch --contains tags/2.6.0-rc1
>     * master
>
> Could you help to check and hopefully fix this?
>
> Thanks!
>
> On Sat, Feb 16, 2019 at 2:44 AM krtaylor <kurt.r.taylor at gmail.com> wrote:
> >
> > I have not been successful (yet) in trying to get access to our
> > openbmc.org website for adding things like announcements. So, I created
> > a quick release announcement on my personal blog to spread the great
> > news about all the hard work that went into this release!
> >
> > http://www.kurttaylor.com/blog/2019/02/openbmc-2-6-release/
> > or
> > https://twitter.com/kurtrtaylor/status/1096473964350791681
> >
> > Kurt Taylor (krtaylor)
> >


More information about the openbmc mailing list