From: Yao Qi <qiyaoltc@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Nitish Kumar Mishra <mishra.nitish.88@gmail.com>,
Pedro Alves <palves@redhat.com>,
Antoine Tremblay <antoine.tremblay@ericsson.com>
Subject: Re: GDB 8.0 release/branching update (10 more days to branching)
Date: Sat, 04 Mar 2017 22:16:00 -0000 [thread overview]
Message-ID: <CAH=s-PNyE=b8B6c527hKg+0fU7FPAMLB=R2w1dFGDtujftxMtA@mail.gmail.com> (raw)
In-Reply-To: <20170304175903.qwbqoqm35raz4dov@adacore.com>
On Sat, Mar 4, 2017 at 5:59 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> So, all in all, at the moment, I don't think we have anything blocking
> for creating the release. But if you know of some other issues, please
> let us know.
>
Two issues in my mind,
I raised some questions on new record Python bindings,
https://sourceware.org/ml/gdb-patches/2017-03/msg00023.html
There is not test fail or regression, but it is about python api,
which can't be changed after they are released. I want to make
them more general, they are too btrace specific so far. This should
be done by release, IMO.
Current GDB mainline failed to build with old python, and Tim
posted a patch https://sourceware.org/ml/gdb-patches/2017-02/msg00712.html
I requested Tim to add test case.
I'll go to Linaro Connect next week. I still check emails, but should
be less active. I'll take some days off afterwards and back to work
on March 16th. Then, I'll seriously start pre-release tests for ARM
and AArch64, and fix bugs if any.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-03-04 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 17:59 Joel Brobecker
2017-03-04 22:16 ` Yao Qi [this message]
2017-03-07 0:26 ` Joel Brobecker
2017-03-07 15:06 ` Pedro Alves
2017-03-09 18:52 ` Andreas Arnez
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='CAH=s-PNyE=b8B6c527hKg+0fU7FPAMLB=R2w1dFGDtujftxMtA@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=antoine.tremblay@ericsson.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=mishra.nitish.88@gmail.com \
--cc=palves@redhat.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