openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: Upcoming OpenBMC release 2.11
Date: Wed, 15 Dec 2021 16:14:10 -0600	[thread overview]
Message-ID: <YbposjOPwc1puNvR@heinlein> (raw)

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

Hello,

It has been almost a year since our last release (2.9).  We created a tag for
2.10.0-rc1 but it was never completed.  We recently created a branch for the
upstream Yocto Honister release and primed it with everything that was in our
`master` plus an update of Yocto to the Honister release branch.

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.

Since there has typically not been tons of demand on release branches and
support of them, this is going to be a low-effort process.  If anyone is
interested in better defining (and executing) a release process going forward,
we are certainly interested in volunteers.

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2021-12-15 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 22:14 Patrick Williams [this message]
2022-01-19 20:00 ` Upcoming OpenBMC release 2.11 Patrick Williams
2022-02-11 10:03   ` Thaj
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=YbposjOPwc1puNvR@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=openbmc@lists.ozlabs.org \
    /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).