lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: "Jérémie Galarneau via lttng-dev" <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Cc: diamon-discuss@lists.linuxfoundation.org,
	linux-trace-users@vger.kernel.org
Subject: [RELEASE] Babeltrace 2.1.2 - Brossard
Date: Tue, 22 Jul 2025 17:38:48 -0400	[thread overview]
Message-ID: <aIAE6K9uksn8l1jf@efficios.com> (raw)

Hi everyone!

Today marks the release of Babeltrace 2.1.2, coinciding with
"National Hammock Day" – the perfect excuse to kick back and relax while
this new release builds.

What's new since Babeltrace 2.1.1?
==================================

Below is the full list of changes in this update:

2025-07-22 Babeltrace 2.1.2 (National Hammock Day)
    * src.ctf.fs: be less strict when encountering trailing byte at the end of packetized CTF 1.8 metadata
    * tests: add bt_test_cli
    * tests: make bt_cli accept non-positional options
    * tests: bt_diff_cli: don't pass unexpected extra args to bt_diff
    * tests: remove unnecessary nonlocal keywords
    * Fix: Python: set local `typing` version to that of 3.5.2
    * Fix: Python: missing __contains__ method for _PluginComponentClasses
    * Fix: tests: Add explicit items method for Mapping compatibility
    * Tests: sync normand.py with upstream
    * Fix: tests: Add explicit __iter__ method for Iterator compatibility
    * Fix: Use local_typing with Python < 3.5.3
    * Update working version to Babeltrace v2.1.2

We've worked hard to address issues and enhance the Babeltrace project, and we
appreciate the community's feedback and contributions. As always, we look
forward to hearing about your experiences with this release and how we can
continue to improve Babeltrace!

Happy coding, and treat yourself to something pecan-related today!

Important links
===============
Babeltrace 2.1.2 tarball:
    https://www.efficios.com/files/babeltrace/babeltrace2-2.1.2.tar.bz2

Babeltrace website:
    https://babeltrace.org

Mailing list (for support and development):
    `lttng-dev at lists.lttng.org`

IRC channel:
    `#lttng` on `irc.oftc.net`

Git repository:
    https://bugs.lttng.org/projects/babeltrace

GitHub project:
    https://github.com/efficios/babeltrace

Continuous integration:
    https://ci.lttng.org/view/Babeltrace/

Code review:
    https://review.lttng.org/q/project:babeltrace

                 reply	other threads:[~2025-07-22 21:39 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=aIAE6K9uksn8l1jf@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    --cc=jeremie.galarneau@efficios.com \
    --cc=linux-trace-users@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).