Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: jbernard@debian.org (Jon Bernard)
Subject: [lttng-dev] LTTng packages in Debian sid out of sync
Date: Sun, 3 Nov 2013 18:19:21 -0500	[thread overview]
Message-ID: <20131103231921.GA6958@shaniqua> (raw)
In-Reply-To: <20131020160434.GA2011@helmut.local>

* Jon Bernard <jbernard at debian.org> wrote:
> * Mathieu Desnoyers <mathieu.desnoyers at efficios.com> wrote:
> > ----- Original Message -----
> > > From: "Jon Bernard" <jbernard@debian.org>
> > > To: "Mathieu Desnoyers" <mathieu.desnoyers at efficios.com>
> > > Cc: "St?phane Graber" <stgraber at ubuntu.com>, "Alexandre Montplaisir" <alexmonthy at voxpopuli.im>,
> > > lttng-dev at lists.lttng.org
> > > Sent: Sunday, October 20, 2013 9:45:21 AM
> > > Subject: Re: LTTng packages in Debian sid out of sync
> > > 
> > [...]
> > > 
> > > That is not exactly what I intended to convey, let me be more direct about my
> > > view.  I completely agree that sid should have 2.3.x immediately.  I also
> > > agree
> > > that 2.3 should be targeted for testing, and therefore the next stable
> > > release.
> > 
> > Allright :) I'm glad we're on the same page, sorry for the misunderstanding.
> 
> No worries.  I'll add that future releases (like the upcoming 2.4) will
> be prepared and tested all together prior to upload - to hopefully avoid
> the previous situation/nightmare that I managed to get myself into.
> 
> There can still be a sizable amount of work for 2.3 to fully land into
> testing, so that is my primary focus.  The freeze deadline is fast
> approaching, so I will be keeping a close eye on things as they
> progress.  As things settle I'll post status here.

lttng-tools 2.3.0 was just accepted, so on sid (unstable) we should now be at
version 2.3.0 across the board.  Things look pretty good to me, but if anyone
has time to test the packages and let me know if something's missing, structured
incorrectly, or not behaving as expected - that would be awesome.

Cheers,

-- 
Jon



       reply	other threads:[~2013-11-03 23:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <630558869.45441.1382211345502.JavaMail.zimbra@efficios.com>
     [not found] ` <856849325.45462.1382211994767.JavaMail.zimbra@efficios.com>
     [not found]   ` <20131019211009.GA83292@helmut.local>
     [not found]     ` <300817690.45707.1382242504740.JavaMail.zimbra@efficios.com>
     [not found]       ` <20131020134521.GA97360@helmut.local>
     [not found]         ` <1084047903.45979.1382281219903.JavaMail.zimbra@efficios.com>
     [not found]           ` <20131020160434.GA2011@helmut.local>
2013-11-03 23:19             ` Jon Bernard [this message]
2013-11-10 14:52               ` Mathieu Desnoyers
2013-11-10 15:21                 ` Jon Bernard
2013-11-10 15:29                   ` Mathieu Desnoyers
2013-11-13  1:42                     ` Yannick Brosseau
2013-11-13 17:01                       ` Jon Bernard
2013-11-14 20:45                         ` Jon Bernard
2013-11-12 15:39               ` David Goulet
2013-11-13 21:02                 ` Jon Bernard
2013-11-13 21:09                   ` David Goulet
2013-11-22 18:57             ` Jon Bernard
2013-11-22 19:02               ` Mathieu Desnoyers

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=20131103231921.GA6958@shaniqua \
    --to=jbernard@debian.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