From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecke@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB Release Managers announcement
Date: Thu, 18 Jun 2026 09:02:46 +0300 [thread overview]
Message-ID: <86eci4idx5.fsf@gnu.org> (raw)
In-Reply-To: <ajLfXPAE9bnlMBMt@adacore.com> (message from Joel Brobecker on Wed, 17 Jun 2026 10:54:36 -0700)
> Date: Wed, 17 Jun 2026 10:54:36 -0700
> From: Joel Brobecker <brobecke@adacore.com>
> Cc: Joel Brobecker <brobecker@adacore.com>
>
> A quick message to let everyone know that I am stepping down from
> my role as GDB Release Manager. Andrew Burgess and Simon Marchi,
> two of GDB's Global Maintainers, have volunteered to take on
> this role in my place. Please join me in thanking them for generously
> offering their time to keep our releases running smoothly.
>
> Attached is the patch to gdb/MAINTAINERS which I will push next
> to master, making the change official.
>
> Speaking for myself, I am deeply thankful for having been trusted with
> this responsibility. Thanks to to hard work of all the contributors,
> testers, Area Maintainers and Global Maintainers, we managed over
> a period of about 20 years to produce almost 60 releases in total.
>
> I'm excited to see such long time contributors as Simon and Andrew
> stepping in. I don't see the project being as active as ever, so
> I look forward to many more releases!
Thank you for doing this job till now, and thanks to Andrew and Simon
for stepping up!
next prev parent reply other threads:[~2026-06-18 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 17:54 Joel Brobecker
2026-06-17 19:39 ` Sergio Durigan Junior
2026-06-18 0:00 ` Jose E. Marchesi
2026-06-18 3:08 ` Thiago Jung Bauermann
2026-06-18 6:02 ` Eli Zaretskii [this message]
2026-06-19 19:27 ` Simon Marchi
2026-07-03 18:42 ` Pedro Alves
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=86eci4idx5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecke@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