From: Philippe Proulx via lttng-dev <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>,
"tracecompass-dev@eclipse.org" <tracecompass-dev@eclipse.org>,
"diamon-discuss@lists.linuxfoundation.org"
<diamon-discuss@lists.linuxfoundation.org>
Subject: [lttng-dev] Upcoming CTF 2 specification
Date: Mon, 4 Mar 2024 16:48:15 +0000 [thread overview]
Message-ID: <YT3PR01MB97235A5745DD33CD2B7D0478D3232@YT3PR01MB9723.CANPRD01.PROD.OUTLOOK.COM> (raw)
To those concerned,
After years of development, the DiaMon Workgroup announces that it will
publish the official specification of the Common Trace Format, version 2
based on its latest release candidate, CTF2-SPECRC-9.0 [1].
Indeed, we now possess sufficient implementation code to be very
confident that CTF2-SPECRC-9.0 does not contain any major errors or
omissions, taking into account the goals of the format.
Consequently, we will publish the CTF2-SPEC-2.0 document in two weeks,
barring any significant and justified objection in response to this
email.
Although its form may change in the future, for instance to add examples
or to make them interactive, its content shall remain as is in
perpetuity. In other words, we do not anticipate to publish
CTF2-SPEC-2.1: any additions or changes, which we will document as part
of new DiaMon documents, will be made through the new metadata stream
attribute [2] or extension [3] instruments.
[1]: https://diamon.org/ctf/files/CTF2-SPECRC-9.0rA.html
[2]: https://diamon.org/ctf/files/CTF2-SPECRC-9.0rA.html#attrs
[3]: https://diamon.org/ctf/files/CTF2-SPECRC-9.0rA.html#ext
I hope you have a very good day,
Philippe Proulx
EfficiOS Inc.
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
reply other threads:[~2024-03-04 16:48 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=YT3PR01MB97235A5745DD33CD2B7D0478D3232@YT3PR01MB9723.CANPRD01.PROD.OUTLOOK.COM \
--to=lttng-dev@lists.lttng.org \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=pproulx@efficios.com \
--cc=tracecompass-dev@eclipse.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 read-only IMAP folder(s) and NNTP newsgroup(s).