From: Gustavo Padovan <gus@collabora.com>
To: "kernelci lists.linux.dev" <kernelci@lists.linux.dev>
Subject: 2025.Q3 updates
Date: Thu, 23 Oct 2025 09:58:26 -0300 [thread overview]
Message-ID: <19a11262ff5.17cec6684679195.2854257421151138524@collabora.com> (raw)
In-Reply-To:
Hello,
We just released a blog post with the recent updates from the project. Check it out:
https://kernelci.org/blog/2025/10/23/kernelci-2025-q3-updates/
The KernelCI community has made significant progress in the past quarter. We've completed the critical transition from legacy KCIDB to Rust-based KCIDB-ng and Dashboard DB for better performance and cloud flexibility, while infrastructure improvements reduced deployment times from hours to under one minute. Two Labs WG launched developing pull-mode architecture for secure lab connections, and Dashboard WG started bi-weekly calls focusing planning features and roadmap. The kci-dev CLI has evolved with Debian/RPM packaging, regression detection, and code coverage analysis, plus a new Hardware Information Registry schema is under review to standardize platform naming. Thanks to the entire community—join us at #kernelci on Libera.chat, or Discord[1]!
Regards,
- Gus
(On behalf of the KernelCI community)
[1] https://kernelci.org/community-contact/
--
Gustavo Padovan
Collabora Ltd.
reply other threads:[~2025-10-23 12:58 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=19a11262ff5.17cec6684679195.2854257421151138524@collabora.com \
--to=gus@collabora.com \
--cc=kernelci@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).