Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <stan@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sourceware.org
Subject: Re: update on the gdb-7.0 branch/release
Date: Mon, 18 May 2009 15:40:00 -0000	[thread overview]
Message-ID: <4A118175.2080109@codesourcery.com> (raw)
In-Reply-To: <20090517213820.GI17566@adacore.com>

Joel Brobecker wrote:
>> So what's the current consensus about an approximate dates for the
>> GDB 7.0 branch and release?
>>     
>
> I'm not really sure. I definitely have some time in July to create
> the release if we're ready, but we might not be. After that, it'll
> probably have to be in September. It's hard to be more accurate,
> as it's all based on volunteer efforts.
>   
July allows time to get in most or all of multiprocess, plus a bunch of 
tracepoint work I've been piling up as local patches. We can revisit the 
question on 1 July or so, see where things are at. I don't think we want 
to go later than September in any case, that makes 1.5 years since 6.8, 
which still seems reasonable albeit longish for a major release number.

Although we're volunteers, we also have employers we can push back on - 
"if 7.0 doesn't happen by September, it will be the end of the world and 
everybody will switch to, uh, Visual Studio". :-)

Stan


      parent reply	other threads:[~2009-05-18 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-05 17:35 Joel Brobecker
2009-05-08 18:28 ` Tom Tromey
2009-05-08 20:51   ` Joel Brobecker
2009-05-17 20:08     ` Eli Zaretskii
2009-05-17 21:38       ` Joel Brobecker
2009-05-18  3:05         ` Eli Zaretskii
2009-05-18 15:40         ` Stan Shebs [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=4A118175.2080109@codesourcery.com \
    --to=stan@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.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