Mirror of the lttng-dev mailing list
 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, lwn@lwn.net
Subject: [RELEASE] Babeltrace 2.1.0-rc1
Date: Thu, 19 Dec 2024 18:25:27 -0500	[thread overview]
Message-ID: <Z2SrZ9ciEYNtKCdr@efficios.com> (raw)

Hi there!

It's been a long journey, but here we are: today we're announcing the
first release candidate of Babeltrace 2.1 “Brossard”! 🥳

┃ Brossard (/ˈbrɒsɑːr/) is a city in southwestern Québec, Canada, on
┃ the South Shore of the Fleuve Saint-Laurent, near Montréal.
┃
┃ Home to the Quartier DIX30 lifestyle complex and the Canadiens'
┃ practice facility, Brossard is defined by its suburban sprawl and
┃ stroads like boulevard Taschereau, seamlessly blending commercial
┃ hubs with car-dependent design.

Our main focus for Babeltrace 2.1 was to bring CTF 2
<https://diamon.org/ctf/> support to the project. This required major
changes across the C API, the Python API, all the official plugins, the
command-line interface, the documentation, as well as several internal
aspects, including the tests. This is because CTF 2 introduces new
concepts which are incompatible with the libbabeltrace 2.0 API, and then
this library is the foundation of all the other parts of the project.

Rest assured, however: Babeltrace 2.1 can still read CTF 1.8 traces and
will continue to.

We published CTF2‑SPEC‑2.0, the CTF 2 specification, last March.
Therefore, as far as we know, there are currently no tracers producing
CTF 2 traces. As for LTTng, we plan to add CTF 2 support in version 2.15
(we're currently wrapping up work on version 2.14).

For you the users, this means there isn't much to try out immediately.
However, it was important for us to release Babeltrace 2.1 well ahead of
LTTng 2.15 to ensure that both will be available together in
distributions, and so that a CTF 2 producer author has a stable reader
available for testing.

NOTE: We'll publish the full release notes as well as the online
documentation (manual pages and C API) when releasing Babeltrace 2.1.0,
most probably next month.

Feel free to reach out if you have any questions or comments.

                                                   — The Babeltrace team

LINKS
=====
Project website:
    https://babeltrace.org/

Download link:
    https://www.efficios.com/files/babeltrace/babeltrace2-2.1.0-rc1.tar.bz2

                 reply	other threads:[~2024-12-19 23:25 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=Z2SrZ9ciEYNtKCdr@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 \
    --cc=lwn@lwn.net \
    /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