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.1 - Brossard
Date: Mon, 14 Apr 2025 17:39:53 -0400 [thread overview]
Message-ID: <Z_2AqUiWV6YyDXVS@efficios.com> (raw)
Hi everyone!
Today marks the release of Babeltrace 2.1.1, coinciding with "Pecan Day" – a
nod to this versatile nut and perhaps a call to enjoy a pecan pie or other
pecan treats after updating to this latest version.
What's new since Babeltrace 2.1.0?
==================================
This release focuses on improving stability, compatibility, and documentation,
addressing issues in the LTTng live source, build process, and API references.
Below is the full list of changes in this update:
2025-04-14 Babeltrace 2.1.1 (Pecan Day)
* src.ctf.lttng-live: remove lttng_live_lazy_msg_init function
* src.ctf.lttng-live: fix comment formatting
* README.adoc: Update working version to 2.1
* fix: export bt_component_class_sink_simple_borrow
* fix: building from the release tarball without flex
* doc/api/libbabeltrace2: use `<code>` i.o. `<span>` in `<dt>`
* Fix: doc/api/libbabeltrace2/Doxyfile.in: set version to 2.1
* babeltrace2-sink.text.pretty(7): add missing default param. value
* Update working version to Babeltrace v2.1.1
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.1 tarball:
https://www.efficios.com/files/babeltrace/babeltrace2-2.1.1.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-04-14 21:40 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=Z_2AqUiWV6YyDXVS@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