From: Joel Brobecker <brobecker@adacore.com>
To: gdb@sourceware.org
Subject: make the GDB 7.2 release sooner?
Date: Thu, 27 May 2010 00:29:00 -0000 [thread overview]
Message-ID: <20100527002906.GG20736@adacore.com> (raw)
Hello,
Here is a thought that came to me while looking at the schedule for
a possible 7.1.1:
- There are only a couple of patches that went into the 7.1 branch
since the 7.1 release, so I'm not sure whether it's worth making
that release or not. I certainly don't mind. We have another month
before the planned date for that corrective release.
- There has been a lot of improvements on the Python API side of
things recently, and I think it'd be nice to release that sooner
rather than later.
So, my proposal is to move the 7.2 release date up a few months to, say,
end of June. That should give us ample time to finish up whatever was
in the works (tracepoints? more Python scripts? etc), before we start
the release process.
What triggered this suggestion is python, but we do have lots of other
things that are worth mentioning (in fact, everything in the NEWS files
is worth mentioning), but to summarize:
- Access to Windows Thread Information Block
- Symbian OS support
- D language support
- New GDBserver features and new remote packets
- some user-level improvements on various commands; of interest to
some is a new "save breakpoints" command.
I should also say that this is independent of whether we decide to do
a 7.1.1 release or not. I'm willing to release both if that makes sense.
Thoughts?
--
Joel
next reply other threads:[~2010-05-27 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 0:29 Joel Brobecker [this message]
2010-05-27 13:59 ` Phil Muldoon
2010-05-27 14:50 ` Joel Brobecker
2010-06-08 21:02 ` Tom Tromey
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=20100527002906.GG20736@adacore.com \
--to=brobecker@adacore.com \
--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