From: Simon Marchi <simon.marchi@ericsson.com>
To: Joel Brobecker <brobecker@adacore.com>, <gdb-patches@sourceware.org>
Subject: Re: heads up: one week to 8.0.1 planned release time
Date: Mon, 28 Aug 2017 21:31:00 -0000 [thread overview]
Message-ID: <cc2e5b1b-b943-600e-a2fa-6e03fb2a3cbd@ericsson.com> (raw)
In-Reply-To: <20170828135048.56es2tsqsog2vuv2@adacore.com>
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
next prev parent reply other threads:[~2017-08-28 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 13:50 Joel Brobecker
2017-08-28 21:31 ` Simon Marchi [this message]
2017-08-31 7:48 ` Joel Brobecker
2017-09-05 16:13 ` Simon Marchi
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=cc2e5b1b-b943-600e-a2fa-6e03fb2a3cbd@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=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).