Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: Florian Weimer <fweimer@redhat.com>,
	lttng-dev@lists.lttng.org,
	Yannick Brosseau <yannick.brosseau@gmail.com>,
	Michael Jeanson <mjeanson@efficios.com>,
	Michel Dagenais <michel.dagenais@polymtl.ca>
Subject: [lttng-dev] lttv: Document project status as unmaintained
Date: Tue, 10 Jan 2023 14:46:42 -0500	[thread overview]
Message-ID: <d17dbab6-5222-7065-ae0e-144687b2efc6@efficios.com> (raw)
In-Reply-To: <87h6wyhd7l.fsf@oldenburg.str.redhat.com>

Hi Florian,

I'll pull your patch into the lttv master branch, but please be aware
that the LTTV project has not seen activity since 2013, is currently
unmaintained, and that we do not plan on doing further releases of this
project. Our efforts were diverted elsewhere on the trace analysis
front, namely into Trace Compass and Babeltrace.

In order to clarify the situation, I will introduce a commit into
LTTV's master branch which will remove Yannick Brosseau from the
maintainer role in the README file, and add this section at the
beginning:

PROJECT STATUS
--------------------------------

The LTTV project is currently unmaintained. If you need up-to-date tools
to view/analyze LTTng traces, please consider the following alternatives:

- Trace Compass (https://www.eclipse.org/tracecompass)
- Babeltrace (https://babeltrace.org)


Thank you Yannick for stepping into the role of maintainer near the
end of this project lifetime.

Michael Jeanson noticed that the lttv Fedora package was orphaned.
He just adopted it and is currently investigating the Fedora
documentation to figure out how to request its removal from Fedora.

For those interested in historical artifacts, I created the lttv
svn repository back in 2003 when I was sitting at the Decelles building
at Ecole Polytechnique, working for Prof. Michel Dagenais:

commit bbdf43d6e0e3bd3f9ade420e81915408cbe4fbba
Author: compudj <compudj@04897980-b3bd-0310-b5e0-8ef037075253>
Date:   Thu May 15 13:07:17 2003 +0000

     Initial repository layout
     
     git-svn-id: http://ltt.polymtl.ca/svn@1 04897980-b3bd-0310-b5e0-8ef037075253

This was the beginning of a fun ride which turned out motivating the
creation of LTTng, the Linux kernel Tracepoints, the Common Trace Format,
Trace Compass, Babeltrace, liburcu, the membarrier(2), and the rseq(2)
system calls.

LTTV had a good 10 years of activity from 2003 to 2013, but it is now high
time to redirect users to Trace Compass and Babeltrace instead.

Thanks,

Mathieu


-- 
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  reply	other threads:[~2023-01-10 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 10:54 [lttng-dev] [PATCH] lttv: C99 compatibility fix Florian Weimer via lttng-dev
2023-01-10 19:46 ` Mathieu Desnoyers via lttng-dev [this message]
2023-01-11 11:01   ` [lttng-dev] lttv: Document project status as unmaintained Florian Weimer 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=d17dbab6-5222-7065-ae0e-144687b2efc6@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=fweimer@redhat.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=michel.dagenais@polymtl.ca \
    --cc=mjeanson@efficios.com \
    --cc=yannick.brosseau@gmail.com \
    /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