From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: next GDB release update: 1 month to planned GDB 8.1.1 release
Date: Mon, 02 Apr 2018 13:33:00 -0000 [thread overview]
Message-ID: <20180402133335.t7xruh72z5cxhj5u@adacore.com> (raw)
Hello Team,
GDB 8.1 has been released 2 months ago, so our normal plans call for
an 8.1.1 release in about a month. It should be towards end of Apr,
beginning of May.
So far, it is looking like the GDB 8.1 release must have been very good,
because we only have 1 open PR marked blocking for 8.1, and 3 closed ones
that were fixed in 8.1.1 (including 1 that's purely documentation).
The open PR is the following:
* [KeithS] PR symtab/23010 (Regression: Assertion: SYMBOL_LANGUAGE (sym) == DICT_LANGUAGE (dict)->la_language)
This is a regression. The PR is unassigned, which creates a risk
that no progress be made on this issue in time for the release.
So I made KeithS its champion (being the one who seems to have
taken the ticket on the RedHat side). Thanks Keith! ;-)
Are there any other serious issues that should be fixed in 8.1.1?
Thank you,
--
Joel
next reply other threads:[~2018-04-02 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 13:33 Joel Brobecker [this message]
2018-04-04 6:51 ` Jan Kratochvil
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=20180402133335.t7xruh72z5cxhj5u@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).