This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: heads up: one week to 8.0.1 planned release time
- From: Simon Marchi <simon dot marchi at ericsson dot com>
- To: Joel Brobecker <brobecker at adacore dot com>, <gdb-patches at sourceware dot org>
- Date: Mon, 28 Aug 2017 23:31:02 +0200
- Subject: Re: heads up: one week to 8.0.1 planned release time
- Authentication-results: sourceware.org; auth=none
- Authentication-results: spf=none (sender IP is ) smtp.mailfrom=simon dot marchi at ericsson dot com;
- References: <20170828135048.56es2tsqsog2vuv2@adacore.com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:99
Hi Joel,
On 2017-08-28 03:50 PM, Joel Brobecker wrote:
> Hello everyone,
>
> The 8.0.1 release is currently planned for next Monday (Sep 4th).
> I took a look at the list of PRs still open, and only found one
> which wasn't a regressions, so I do not consider it blocking.
Were you talking about #21827 ? If so I think it's a regression.
Either way, I pushed the proposed patch to both master and gdb-8.0-branch.
> I also looked at the list of PRs fixed since 8.0. It must have been
> a very good release, since we only fixed 5 PRs since then!
>
> Anything blocking that we need to be aware of?
Yao found recently that remote multi-arch exec was broken, see this thread:
https://sourceware.org/ml/gdb-patches/2017-08/msg00488.html
I filed a PR:
https://sourceware.org/bugzilla/show_bug.cgi?id=22021
and added it to the "maybe" list. I have posted a series to fix it
in the thread, it just needs some reviewing :)
> Assuming nothing comes up, should we go ahead with the 8.0.1 release
> next week, or do we want to wait a bit to see if we can find other
> issues we might want to fix before 8.0.1 comes out? (personally,
> I would go ahead with the 8.0.1, with the option of scheduling
> 8.0.2 if we end up finding something we really want for the 8.0.x
> branch; otherwise, 8.1 will be a mere 3 months later).
>
> Thanks!
Fine with me, assuming we can get this multi-arch exec issue sorted out
by then (or decide it's not important enough).
Simon