From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: OpenBMC List <openbmc@lists.ozlabs.org>, Thaj <tajudheenk@gmail.com>
Subject: Re: Upcoming OpenBMC release 2.11
Date: Thu, 17 Feb 2022 09:57:36 -0500 [thread overview]
Message-ID: <4AF3D7E9-4752-4AF5-B556-BAD50F9560BD@fuzziesquirrel.com> (raw)
In-Reply-To: <YgbNmq8SVgJMHXcn@heinlein>
> On Feb 11, 2022, at 3:56 PM, Patrick Williams <patrick@stwcx.xyz> wrote:
>
> 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.
We have a 2.11.0 tag now.
prev parent reply other threads:[~2022-02-17 14:58 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
2022-02-17 14:57 ` Brad Bishop [this message]
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=4AF3D7E9-4752-4AF5-B556-BAD50F9560BD@fuzziesquirrel.com \
--to=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).