From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: GDB 18 release schedule proposal
Date: Sat, 18 Jul 2026 21:10:14 +0100 [thread overview]
Message-ID: <87fr1gcb4p.fsf@redhat.com> (raw)
It's time to start thinking about the GDB 18.x release cycle.
After many years, Joel is handing off release manager responsibilities to
Simon and me (Andrew). Joel has kindly agreed to help us with this first
release, but please have patience while we learn the process.
The proposed branch date for GDB 18 is: August 6th.
The target release date will be no earlier than: September 14th. As
always, this release date will depend on any outstanding issues being
resolved.
Let me know if there are any issues with the proposed schedule, or if
there are any GDB issues which should be resolved before we branch.
We are keen that all three of us be around for each stage of this
release in order to learn the process. As a result, the dates given
above could slip if there are any scheduling conflicts. I'll try to give
as much notice as possible if this happens.
Thanks,
Andrew
reply other threads:[~2026-07-18 20:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87fr1gcb4p.fsf@redhat.com \
--to=aburgess@redhat.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