Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: christian.babeux@efficios.com (Christian Babeux)
Subject: [lttng-dev] [RELEASE] LTTng-UST 2.3.0-rc2
Date: Fri, 30 Aug 2013 15:27:32 -0400	[thread overview]
Message-ID: <CAGDH53nKQw1G81mY2ZnVx5Qi4fiLXsbHC=wjf8uaudab7atB2Q@mail.gmail.com> (raw)
In-Reply-To: <5220EC0D.1040301@ericsson.com>

FYI, I posted a month ago in the "LTTng project development activities
August 2013" thread:

"- We are currently in code freeze for the release candidate phase of
version 2.3. Please use and test this release candidate and report
bugs on our bug tracker [2]. We are aiming for a stable release at the
end of August."

So we announced the final release plan a month ago.

Also, we have contributors, testers and users from around the globe ;)

Christian

On Fri, Aug 30, 2013 at 3:01 PM, Matthew Khouzam
<matthew.khouzam at ericsson.com> wrote:
> I would like to highlight that this means you are releasing on a
> statutory holiday in canada. Also, you are announcing this Friday
> afternoon. :)
>
>
> On 13-08-30 02:41 PM, Mathieu Desnoyers wrote:
>> LTTng-UST, the Linux Trace Toolkit Next Generation Userspace Tracer, is
>> port of the low-overhead tracing capabilities of the LTTng kernel tracer
>> to user-space. The library "liblttng-ust" enables tracing of
>> applications and libraries.
>>
>> We plan a final release on Monday, September 1st. Please let us know
>> quickly if you find issues!
>>
>> Changelog:
>> 2013-08-30 lttng-ust 2.3.0-rc2
>>         * doc/examples/gen-tp: pass automake CPPFLAGS/CFLAGS/LDFLAGS
>>         * tools/lttng-gen-tp: honor CPPFLAGS and LDFLAGS
>>         * Fix: doc/examples cross-build
>>         * Fix: liblttng_ust.la should depend on liblttng-ust-tracepoint.la
>>         * Introduce configure --with-lttng-system-rundir
>>         * examples: tracepoint probes don't need extern C
>>         * Tracepoint probes don't need extern C
>>         * Add trace support for memalign and posix_memalign
>>         * malloc instrumentation: remove dependency on pthread
>>         * Add trace support for calloc and realloc.
>>         * Fix: allow make check to run in VPATH build
>>         * Update .gitignore
>>         * Update obsolete benchmark test
>>         * Cleanup tests (2nd commit)
>>         * Cleanup tests
>>         * Fix: doc/examples VPATH build
>>
>> Project website: http://lttng.org
>> Download link: http://lttng.org/download
>> (please refer to the README file for installation instructions)
>>
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev



      parent reply	other threads:[~2013-08-30 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 18:41 Mathieu Desnoyers
2013-08-30 19:01 ` Matthew Khouzam
2013-08-30 19:06   ` Mathieu Desnoyers
2013-08-30 19:27   ` Christian Babeux [this message]

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='CAGDH53nKQw1G81mY2ZnVx5Qi4fiLXsbHC=wjf8uaudab7atB2Q@mail.gmail.com' \
    --to=christian.babeux@efficios.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