From: Luis Chamberlain <mcgrof@kernel.org>
To: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
linux-cxl@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-kselftest@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, mcgrof@kernel.org
Subject: [ANN]: kdevops v6.2 released devices
Date: Fri, 24 Feb 2023 15:10:26 -0800 [thread overview]
Message-ID: <Y/lD4kVcPqUppMwm@bombadil.infradead.org> (raw)
I'd like to announce the release of kdevops v6.2 [0] [1]. I had already written
about most of the new features on the v6.2-rc1 release in the December 2022
notes [2], but since a new features cannot regress we've seen a few more new
features sneak in since then. I'll re-iterate a few of the newest major
features added since our last release (v5.0.2):
* ZNS
* CXL
* NFS
* Initial Kernel selftests suport: firmware, sysctl, kmod
* OCI cloud support
* libvirt use 9p now for local builds
* PCI-passthrough support including a new dynamic kconfig interface for it
* Building qemu for you
* 12 btrfs profiles to test
* Results for tests are now archived see workflows/fstests/results/
for an example namespace
For more details of release notes you can refer to the v6.2-rc1 [3] and
v6.2 [4] git tags.
Thanks a lot to the developers who have contributed:
Adam Manzanares
Amir Goldstein
Chandan Babu R
Jeff Layton
Joel Granados
Josef Bacik
Luis Chamberlain
Pankaj Raghav
*If* it makes sense, we may set up a stable brach for v6.2.y releases so
which could fixate on the vagrant setup, so that folks using libvirt
can get fixes. If we do that it would make sense to just merge fixes
to the master branch first before the stable branch as well just as we
do in upstream linux / stable branches.
Luis
[0] https://github.com/linux-kdevops/kdevops
[1] https://gitlab.com/linux-kdevops/kdevops
[2] https://people.kernel.org/mcgrof/kdevops-v6-2-rc1-released
[3] https://github.com/linux-kdevops/kdevops/releases/tag/v6.2-rc1
[4] https://github.com/linux-kdevops/kdevops/releases/tag/v6.2
reply other threads:[~2023-02-24 23:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Y/lD4kVcPqUppMwm@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-nfs@vger.kernel.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).