From: Patrick Williams <patrick@stwcx.xyz>
To: OpenBMC List <openbmc@lists.ozlabs.org>
Subject: OpenBMC 2.12 release candidate
Date: Fri, 29 Jul 2022 11:01:59 -0500 [thread overview]
Message-ID: <YuQEd4Ql+r0IVfPK@heinlein.stwcx.org.github.beta.tailscale.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
Hello,
Yocto 4.0 (kirkstone) was released back in April and around the same
time I had branched our own openbmc/kirkstone to match. I've been
keeping this branch updated as upstream kirkstone fixes have come but we
haven't made an official OpenBMC 2.12 release yet.
I just made two new tags in our repository: 2.12.0-rc1 and 2.13.0-dev.
- 2.12.0-rc1 is the tip of openbmc/kirkstone and intended to be the
release candidate for OpenBMC 2.12.
- 2.13.0-dev is the point of split between openbmc/kirkstone and
openbmc/master (really 1 commit later on master). This causes
`git describe` (and corresponding /etc/os-release files in builds)
to show 2.13.0-dev now.
I will leave kirkstone / 2.12.0-rc1 open for 2 weeks for downstream
users to report issues. If there are no reported problems (or just
minor problems that we're not going to backport fixes for), by
August 12th, 2022, then I'll tag 2.12.0.
As usual, we'd appreciate any downstream testing that contributors can
provide.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-07-29 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 16:01 Patrick Williams [this message]
2022-11-03 16:30 ` OpenBMC 2.12 release candidate Patrick Williams
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=YuQEd4Ql+r0IVfPK@heinlein.stwcx.org.github.beta.tailscale.net \
--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).