From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: GDB 15 Release - time to start the process? (2024-02-11)
Date: Sun, 11 Feb 2024 08:54:54 +0400 [thread overview]
Message-ID: <ZchTHkHuRGwArvSk@adacore.com> (raw)
Hi everyone,
What do people think of aiming for sometime in April for our next
GDB 15.1 release? This is the month the current schedule says we are
aiming for. We're slightly behind due to the 14.1 release having come
out a month later than targeted, but I think we can still aim for Apr
by starting now. There's been enough development on master to justify
a release.
Are there issues that you think should be fixed for release 15? If
yes, can you let us know here? (if there is a corresponding GDB PR,
all the better)
Right now, I looked at the list of PRs marked for 15.1, and there is
one:
* [TomT] symtab/31361
.debug_names uses wrong form for DW_IDX_die_offset
https://sourceware.org/bugzilla/show_bug.cgi?id=31361
Anything else?
Thank you!
--
Joel
next reply other threads:[~2024-02-11 4:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 4:54 Joel Brobecker [this message]
2024-02-12 18:57 ` 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=ZchTHkHuRGwArvSk@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).