From: Patrick Williams <patrick@stwcx.xyz>
To: Thaj <tajudheenk@gmail.com>
Cc: OpenBMC List <openbmc@lists.ozlabs.org>,
Brad Bishop <bradleyb@fuzziesquirrel.com>
Subject: Re: Upcoming OpenBMC release 2.11
Date: Fri, 11 Feb 2022 14:56:58 -0600 [thread overview]
Message-ID: <YgbNmq8SVgJMHXcn@heinlein> (raw)
In-Reply-To: <CAH2KKeY_aGKzp+BjYJPagjWAR2WLuqeib4aPy2nBjSc4_ed_zg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
On Fri, Feb 11, 2022 at 03:33:12PM +0530, Thaj wrote:
> Hi Patrick,
Hello Thaj,
>
> 2.9 is quiet old. There are a lot of changes after that. A newer u-boot
> with secure boot support, better AST2600 support etc. A new release is
> necessary.
It seems that not many people who are active contributors in the community
actually care about releases, so there hasn't been much effort put into it.
You used the word "necessary". Would you care to expand, for the community,
what your use case is where you rely on releases?
> There is no 2.11.0-rc1 yet. Is it possible to initiate a release
> process?
The honister branch is effectively the '2.11.0-rc'. I don't have permissions
to create tags myself. I'll see if Brad has bandwidth to create a tag in the
near future.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-11 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 22:14 Upcoming OpenBMC release 2.11 Patrick Williams
2022-01-19 20:00 ` Patrick Williams
2022-02-11 10:03 ` Thaj
2022-02-11 20:56 ` Patrick Williams [this message]
2022-02-17 14:57 ` Brad Bishop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YgbNmq8SVgJMHXcn@heinlein \
--to=patrick@stwcx.xyz \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=tajudheenk@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.