From: "Jérémie Galarneau" <jeremie.galarneau@efficios.com>
To: lttng-dev@lists.lttng.org
Cc: diamon-discuss@lists.linuxfoundation.org
Subject: [diamon-discuss] [RELEASE Babeltrace 2.0.3 - Amqui
Date: Thu, 23 Apr 2020 18:01:40 -0400 [thread overview]
Message-ID: <20200423220140.GA371570@gmail.com> (raw)
Hi everyone!
Today we're releasing the third patch-level release of Babeltrace 2.0
"Amqui".
What's new since Babeltrace 2.0.2?
==================================
This release contains a number of fixes, but more importantly an
initial documentation for the Python bindings.
Note that I messed up and pushed out a later commit tagged as v2.0.3
and retagged the release commit as v2.0.3 again.
If you got the wrong tag, and want the new one, please delete the old
one and fetch the new one by doing:
git tag -d v2.0.3
git fetch origin tag v2.0.3
to get the updated tag.
You can test which tag you have by doing
git rev-parse v2.0.3
which should return 91d15447 if you have the new version.
Sorry for the inconvenience.
The full change log follows.
2020-04-24 Babeltrace 2.0.3 (German Beer Day)
* Fix: lib: use appropriate format specifier to print message iterator class
* Fix: sink.text.pretty: check that port is connected before creating message iterator
* Add initial Python bindings documentation
* Fix: bt2: read properties on _DiscardedEventsMessage
* tests: add tests for discarded events/packets creation
* Fix: bt2: add precond. check, for stream class supporting discarded msgs with clock snapshot without clock class
* Fix: flt-utils.muxer: reference leak in muxer_msg_iter_add_upstream_msg_iter error path
* Fix: sink.text.details: goto error when failing to add input port
* Fix: src.text.dmesg: add missing assignment of `status` on error path
* Revert "bt2: _EventConst.__getitem__(): use a single temporary variable"
* Fix: src.ctf.fs: initialize the other_entry variable
* bt2: _EventConst.__getitem__(): use a single temporary variable
* Fix: _EventConst.__getitem__(): check if event has a packet
* doc: bt_field_class...get_mapping_labels...(): clarify RV's validity
* doc/api/libbabeltrace2/style.css: make font weight of `.intertd` normal
* Update working version to Babeltrace 2.0.3
Important links
===============
Babeltrace 2.0.3 tarball:
https://www.efficios.com/files/babeltrace/babeltrace2-2.0.3.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:[~2020-04-23 22:01 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=20200423220140.GA371570@gmail.com \
--to=jeremie.galarneau@efficios.com \
--cc=diamon-discuss@lists.linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox