From: Joel Brobecker <brobecker@adacore.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb@sourceware.org
Subject: Re: GDB 7.1 release planning...
Date: Sat, 09 Jan 2010 03:31:00 -0000 [thread overview]
Message-ID: <20100109033134.GC27914@adacore.com> (raw)
In-Reply-To: <4B47C3CE.3070307@codesourcery.com>
> In any case, I think the gdbserver bits are sufficiently exciting to
> be worth pushing back 7.1 by a couple weeks. Plus we lose some
> momentum if new tracepoint features are in 7.1, but target-side code
> with which to try them out doesn't show up until 7.2.
I think that would be fine - I don't want the dates, which are somewhat
chose arbitrarily on a roughly-6-months-calendar, to hurt certain new
features. We pretty much did the same for Python the last time. Also,
I don't think people are waiting for 7.1 with as much anticipation as
they did for 7.0. It took a lot of time and effort before we were ready!
New proposed dates: Branch & Pre-release: Feb 10. That's 3 extra weeks.
Are you guys pretty confident you can make it? That would put the
tentative a couple of weeks later, around Feb 24 [1].
--
Joel
[1]: Note that I will not be available Feb 20-24 (incl), and then Mar 01-02.
next prev parent reply other threads:[~2010-01-09 3:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 4:21 Joel Brobecker
2010-01-08 9:24 ` Tristan Gingold
2010-01-08 11:08 ` Joel Brobecker
2010-01-08 13:49 ` Jan Kratochvil
2010-01-08 18:44 ` Michael Snyder
2010-01-09 3:08 ` Joel Brobecker
2010-01-08 13:53 ` Daniel Jacobowitz
2010-01-08 16:14 ` Tom Tromey
2010-01-09 3:18 ` Joel Brobecker
2010-01-11 19:58 ` Tom Tromey
2010-01-14 4:54 ` Joel Brobecker
2010-01-08 19:28 ` Stan Shebs
2010-01-08 22:32 ` Pedro Alves
2010-01-08 23:46 ` Stan Shebs
2010-01-09 3:31 ` Joel Brobecker [this message]
2010-01-09 16:52 ` Marc Khouzam
2010-01-11 9:48 ` Joel Brobecker
2010-01-11 14:31 ` Pedro Alves
2010-01-11 14:36 ` Pedro Alves
2010-01-13 23:17 ` Michael Snyder
2010-01-14 3:30 ` Joel Brobecker
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=20100109033134.GC27914@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=stan@codesourcery.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