Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: time to start thinking about GDB 7.3 (as well!)
Date: Mon, 14 Feb 2011 14:52:00 -0000	[thread overview]
Message-ID: <20110214145010.GX2384@adacore.com> (raw)

According to the tentative calendar, it's also time to start thinking
about the GDB 7.3 release process.  Normally, we were planning on
branching next week.

Judging from the entries in the NEWS file, I think we have enough
material to make a new release.  However, I also believe that the
same issues that we identified as a blocker for 7.2.1 are also
relevant for 7.3.

There is a Wiki page for the 7.3 release:
    http://sourceware.org/gdb/wiki/GDB_7.3_Release

Can we start putting entries for things we know need to be fixed
before branching/release?

We should also discuss features that we think would be worthwhile
waiting for. Some Python work being finished, for instance, which
might nicely complements some of the new enhancements we got?
Tracepoints? gdbserver work? Etc.

What I propose is to produce 7.2.1 as soon as the blocking issues
are fixed.  We might also be creating the 7.3 branch pretty much
at the same time, which means that 7.3 might be coming shortly
after 7.2.1, but I think that's OK. I'd rather not have a 7.2.1
if that means artificially delaying 7.3 - but I don't a problem
with producing both.

-- 
Joel


             reply	other threads:[~2011-02-14 14:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 14:52 Joel Brobecker [this message]
2011-02-14 19:33 ` Tom Tromey
2011-02-14 20:15 ` Mike Frysinger
2011-03-07 11:27   ` Mike Frysinger
2011-03-07 11:43     ` Pedro Alves
2011-03-07 12:35       ` Joel Brobecker
2011-03-07 15:44         ` Pedro Alves
2011-02-15  4:06 ` Hui Zhu

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=20110214145010.GX2384@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@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