Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: time to create the GDB 8.1.x branch?
Date: Tue, 21 Nov 2017 12:39:00 -0000	[thread overview]
Message-ID: <9b725473-9732-ff68-f0f2-b8a702d81c81@redhat.com> (raw)
In-Reply-To: <20171120191510.clz2ywdyknuftzrh@adacore.com>

On 11/20/2017 07:15 PM, Joel Brobecker wrote:
> Hello,
> 
> I think it is time to start thinking about the next release (8.1),
> as it has been 5.5 months since we release 8.0, and 7 months
> since we created the 8.0.x branch!

W00t, already! :-P

> 
> I've created the following wiki page for keeping track of this release
> cycle:
> 
>     https://sourceware.org/gdb/wiki/GDB_8.1_Release
> 
> Looking at the gdb/NEWS file, it shows a fair number of enhancements.
> Also, outside of one GDB PR that was marked for 8.1 but is no longer
> critical IMO, we have no PR active targetting 8.1.
> 
> Are there any changes that would be worth waiting for before we branch
> 8.1? If not, I plan on creating the branch next Monday (Nov 27th).

I'd like to get the rest of the C++ breakpoint improvements series in.

A good part of it is in, which already fixed many user-visible things,
but the NEWS change hasn't yet:
  https://sourceware.org/ml/gdb-patches/2017-06/msg00594.html

The remaining part is the support for wild matching (ignore
leading classes/namespaces) for C++, and support for breakpoints on
symbols with ABI tags.
Keith reviewed the whole series but I haven't gotten around to
addressing his comments on that part of the series yes (since
only recently that lookup_name_info patch got in).  I'll try
to do that ASAP.

Thanks,
Pedro Alves


  parent reply	other threads:[~2017-11-21 12:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 19:15 Joel Brobecker
2017-11-21 10:50 ` Ulrich Weigand
2017-11-27 21:55   ` Joel Brobecker
2017-11-28 19:44     ` Ulrich Weigand
2017-11-28 20:32       ` Pedro Alves
2017-11-29 13:20         ` Pedro Alves
2017-11-29 21:00           ` Joel Brobecker
2017-11-29 21:49             ` Pedro Alves
2017-11-29 22:20               ` Joel Brobecker
2017-11-21 11:10 ` Yao Qi
2017-11-21 12:39 ` Pedro Alves [this message]
2017-11-27 22:20   ` Joel Brobecker
2017-11-27 22:41     ` Pedro Alves
2017-11-29 20:56       ` Joel Brobecker
2017-11-29 22:20         ` Pedro Alves
2017-11-29 22:46           ` Joel Brobecker
2017-11-22 13:07 ` Yao Qi
2017-11-27 22:06   ` Joel Brobecker
2017-11-27 22:14     ` Joel Brobecker
2017-11-28 12:38     ` Yao Qi
2017-11-29 20:58       ` Joel Brobecker
2017-11-22 18:03 ` Sergio Durigan Junior
2017-11-27 22:23   ` Joel Brobecker
2017-11-28 17:08     ` Sergio Durigan Junior
2017-11-23 15:16 ` Pedro Alves
2017-11-23 16:50   ` Joel Brobecker
2017-11-23 17:32     ` 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=9b725473-9732-ff68-f0f2-b8a702d81c81@redhat.com \
    --to=palves@redhat.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