From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: GDB 9.1 release: Start of stabilization period ?
Date: Sun, 13 Oct 2019 01:19:00 -0000 [thread overview]
Message-ID: <CAPTJ0XFx7hUtjNxZLCV9OUOgMaN+fZ2-o_rHQ3sPJX4KT14rZw@mail.gmail.com> (raw)
In-Reply-To: <20191012191938.GA2675@adacore.com>
HI Joel,
On Sat, Oct 12, 2019 at 3:19 PM Joel Brobecker <brobecker@adacore.com> wrote:
>
> Hi everyone,
>
> Now that the 8.3.1 release is out, I think now is a good time to
> prepare the 9.1 release. I looked at the gdb/NEWS file and it is
> chockablock full of goodies!
>
> At the moment, there aren't any issues in bugzilla that are marked
> pending for GDB 9.1.
>
> Are there any issues that people would like to be fixed, before
> we release GDB 9.1? For those issues, it would be good to see whether
> these are blocking issues prior to branching, or not.
>
> In the meantime, while we start collecting the list of issues
> we want to fix for 9.1, if there aren't any objection, I'd like us
> to start a cooling period so as to stabilize GDB prior to branching.
I'm not that familiar with the gdb release process, but there are two
changes that I was hoping could be part of the next release:
- The threaded symbol loading that tromey (and I) have been working on
- My patch here: https://sourceware.org/ml/gdb-patches/2019-10/msg00125.html
Thanks,
Christian
next prev parent reply other threads:[~2019-10-13 1:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 19:19 Joel Brobecker
2019-10-13 1:19 ` Christian Biesinger via gdb-patches [this message]
2019-10-13 13:58 ` Tom de Vries
2019-10-15 15:20 ` Joel Brobecker
2019-10-15 15:23 ` Tom de Vries
2019-10-15 15:37 ` Joel Brobecker
2019-10-15 15:16 ` Joel Brobecker
2019-10-13 14:35 ` Philippe Waroquiers
2019-10-15 15:37 ` Joel Brobecker
2019-10-14 17:44 ` Tom Tromey
2019-10-15 15:53 ` Joel Brobecker
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=CAPTJ0XFx7hUtjNxZLCV9OUOgMaN+fZ2-o_rHQ3sPJX4KT14rZw@mail.gmail.com \
--to=gdb-patches@sourceware.org \
--cc=brobecker@adacore.com \
--cc=cbiesinger@google.com \
/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