Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Maxime Ripard <mripard@redhat.com>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: tools@kernel.org, users@kernel.org
Subject: Re: b4 0.16.0 released
Date: Tue, 11 Aug 2026 17:15:15 +0200	[thread overview]
Message-ID: <20260811-honest-python-of-fame-c3ddbf@houat> (raw)
In-Reply-To: <20260810-magnificent-precious-frog-f3d1ca@meerkat>

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

On Mon, Aug 10, 2026 at 03:08:28PM -0400, Konstantin Ryabitsev wrote:
> On Mon, Aug 10, 2026 at 11:47:21AM -0400, Konstantin Ryabitsev wrote:
> > > > Full release notes available here:
> > > > https://b4.docs.kernel.org/en/latest/releases.html
> > > 
> > > It looks like the tarball hasn't been published? Is it on purpose?
> > 
> > Oh, sorry, I forgot about that step! I needed to first make sure that the two
> > new libraries have tarballs, too, and then got busy with bot wars.
> > 
> > I'll set it up today, thanks for the reminder.
> 
> All tarballs should be in place now.

Thanks, I did the Fedora new package requests for the two new libraries:
https://bugzilla.redhat.com/show_bug.cgi?id=2513852
https://bugzilla.redhat.com/show_bug.cgi?id=2513973

I'll work on the 0.16.0 update next

Maxime

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

  reply	other threads:[~2026-08-11 15:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 17:01 b4 0.16.0 released Konstantin Ryabitsev
2026-08-10 11:51 ` Maxime Ripard
2026-08-10 15:47   ` Konstantin Ryabitsev
2026-08-10 19:08     ` Konstantin Ryabitsev
2026-08-11 15:15       ` Maxime Ripard [this message]
2026-08-14  9:31         ` Maxime Ripard

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=20260811-honest-python-of-fame-c3ddbf@houat \
    --to=mripard@redhat.com \
    --cc=mricon@kernel.org \
    --cc=tools@kernel.org \
    --cc=users@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