openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Thaj <tajudheenk@gmail.com>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Re: Upcoming OpenBMC release 2.11
Date: Fri, 11 Feb 2022 15:33:12 +0530	[thread overview]
Message-ID: <CAH2KKeY_aGKzp+BjYJPagjWAR2WLuqeib4aPy2nBjSc4_ed_zg@mail.gmail.com> (raw)
In-Reply-To: <YehtxgLG3KlzKFAk@heinlein>

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

Hi Patrick,

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. There is no 2.11.0-rc1 yet. Is it possible to initiate a release
process?

Regards,
Thaj

On Thu, 20 Jan 2022, 01:30 Patrick Williams, <patrick@stwcx.xyz> wrote:

> Reminder...
>
> On Wed, Dec 15, 2021 at 04:14:10PM -0600, Patrick Williams wrote:
> > What I'd like to do is target January 14th, 2022 for our 2.11 release.
> If you
> > are interested in your systems working on that release branch, please
> test the
> > 'honister' branch and let me know of any issues you see either here or in
> > #release-planning.
>
> I have not heard from anyone on interest in a 2.11 release.
>
> --
> Patrick Williams
>

[-- Attachment #2: Type: text/html, Size: 1243 bytes --]

  reply	other threads:[~2022-02-11 10:04 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 [this message]
2022-02-11 20:56     ` Patrick Williams
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=CAH2KKeY_aGKzp+BjYJPagjWAR2WLuqeib4aPy2nBjSc4_ed_zg@mail.gmail.com \
    --to=tajudheenk@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    /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).