All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérémie Galarneau" <jeremie.galarneau@efficios.com>
To: lttng-dev@lists.lttng.org
Cc: diamon-discuss@lists.linuxfoundation.org,
	linux-trace-users@vger.kernel.org
Subject: [RELEASE] Babeltrace 2.0.6 - Amqui
Date: Thu, 28 Mar 2024 15:48:37 -0400	[thread overview]
Message-ID: <ZgXJlRnySWf3l-JN@efficios.com> (raw)

Hi everyone!

Today marks the release of Babeltrace 2.0.6, coinciding with "Respect Your Cat
Day" – a nod to our feline friends and perhaps a call to enjoy a moment of
relaxation after updating to this latest version.

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

This release brings an assortment of fixes and improvements across the board.

Highlights include numerous fixes to ensure the compatibility of the Python
bindings with newer Python versions, enhancements for handling inactive streams
in the LTTng live source, and various documentation and test suite refinements.

Below is the full list of changes in this update:

2024-03-28 Babeltrace 2.0.6 (Respect Your Cat Day)
    * bt2: disable some warnings for `native_bt.c`
    * bt2: compile `native_bt.c` with `-Wno-undef`
    * Fix: src.ctf.lttng-live: expect NEW_STREAM/METADATA for inactive streams
    * Fix: `babeltrace2 convert`: don't consider the `--plugin-path` opt.
    * include/babeltrace2/plugin/plugin-dev.h: "define" -> "definition
    * Fix: doc: escape double quote in bt_p alias
    * Fix: bt2: pass _TraceClassConst to destruction listeners
    * fix: 'load_module()' deprecated in Python 3.12
    * tests: retry os.rename on PermissionError failure in lttng_live_server.py
    * doc: fix uptream -> upstream typos
    * fix: test_message_iterator.py hangs on Python 3.12
    * plugin-dev: mark symbols meant to be public with __attribute__((visibility("default")))
    * Silence -Wunused-but-set-variable error with clang
    * Fix: Windows DLL path lookup with Python >= 3.8
    * doc/man: make default values of boolean init. params. clearer
    * RFC: docs: fix: Match stated automake requirement
    * fix: make flake8 6.x happy
    * fix: running black on python 3.11
    * bt_query_executor_create_with_method_data(): fix docs note
    * Fix: ctf-writer: null dereference in bt_ctf_trace_common_add_stream_class
    * Update working version to Babeltrace v2.0.6

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!

As we celebrate the release of Babeltrace 2.0.6, let's also take a moment to
appreciate our feline companions, who often keep us company during those long
debugging sessions.

Happy coding, and give your cat (or pet of choice) some extra respect today!

Important links
===============
Babeltrace 2.0.6 tarball:
    https://www.efficios.com/files/babeltrace/babeltrace2-2.0.6.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

WARNING: multiple messages have this Message-ID (diff)
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: [lttng-dev] [RELEASE] Babeltrace 2.0.6 - Amqui
Date: Thu, 28 Mar 2024 15:48:37 -0400	[thread overview]
Message-ID: <ZgXJlRnySWf3l-JN@efficios.com> (raw)

Hi everyone!

Today marks the release of Babeltrace 2.0.6, coinciding with "Respect Your Cat
Day" – a nod to our feline friends and perhaps a call to enjoy a moment of
relaxation after updating to this latest version.

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

This release brings an assortment of fixes and improvements across the board.

Highlights include numerous fixes to ensure the compatibility of the Python
bindings with newer Python versions, enhancements for handling inactive streams
in the LTTng live source, and various documentation and test suite refinements.

Below is the full list of changes in this update:

2024-03-28 Babeltrace 2.0.6 (Respect Your Cat Day)
    * bt2: disable some warnings for `native_bt.c`
    * bt2: compile `native_bt.c` with `-Wno-undef`
    * Fix: src.ctf.lttng-live: expect NEW_STREAM/METADATA for inactive streams
    * Fix: `babeltrace2 convert`: don't consider the `--plugin-path` opt.
    * include/babeltrace2/plugin/plugin-dev.h: "define" -> "definition
    * Fix: doc: escape double quote in bt_p alias
    * Fix: bt2: pass _TraceClassConst to destruction listeners
    * fix: 'load_module()' deprecated in Python 3.12
    * tests: retry os.rename on PermissionError failure in lttng_live_server.py
    * doc: fix uptream -> upstream typos
    * fix: test_message_iterator.py hangs on Python 3.12
    * plugin-dev: mark symbols meant to be public with __attribute__((visibility("default")))
    * Silence -Wunused-but-set-variable error with clang
    * Fix: Windows DLL path lookup with Python >= 3.8
    * doc/man: make default values of boolean init. params. clearer
    * RFC: docs: fix: Match stated automake requirement
    * fix: make flake8 6.x happy
    * fix: running black on python 3.11
    * bt_query_executor_create_with_method_data(): fix docs note
    * Fix: ctf-writer: null dereference in bt_ctf_trace_common_add_stream_class
    * Update working version to Babeltrace v2.0.6

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!

As we celebrate the release of Babeltrace 2.0.6, let's also take a moment to
appreciate our feline companions, who often keep us company during those long
debugging sessions.

Happy coding, and give your cat (or pet of choice) some extra respect today!

Important links
===============
Babeltrace 2.0.6 tarball:
    https://www.efficios.com/files/babeltrace/babeltrace2-2.0.6.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
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2024-03-28 19:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-28 19:48 Jérémie Galarneau [this message]
2024-03-28 19:48 ` [lttng-dev] [RELEASE] Babeltrace 2.0.6 - Amqui Jérémie Galarneau via lttng-dev

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=ZgXJlRnySWf3l-JN@efficios.com \
    --to=jeremie.galarneau@efficios.com \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    --cc=linux-trace-users@vger.kernel.org \
    --cc=lttng-dev@lists.lttng.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.