From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: NEED FEEDBACK: time to start the GDB 8.2 release process (2018-05-30 update)
Date: Thu, 31 May 2018 19:40:00 -0000 [thread overview]
Message-ID: <87efhrvfkb.fsf@redhat.com> (raw)
In-Reply-To: <20180530225306.jbf5xtpgvkmno7md@adacore.com> (Joel Brobecker's message of "Wed, 30 May 2018 15:53:06 -0700")
On Wednesday, May 30 2018, Joel Brobecker wrote:
> Hey everyone,
Hey Joel,
As usual, thanks for taking care of the release!
> Although 8.1.1 is not entirely out yet, I think we should start working
> on GDB 8.2 now, rather than wait more. Looking at the NEWS files,
> we have a reasonable list of new features to warrant a new release.
>
> The initial plan, published at https://www.sourceware.org/gdb/schedule/,
> called for a branch on Jun 15th, so 2 weeks from now. In internet time,
> this is quite a short time-frame, but perhaps we'll be able to make it?
>
> Does anyone have projects that are nearly finished and would be
> important to include in 8.2 rather than wait for 8.3? If yes,
> what kind of time frame can we expect for getting those in.
> Should we wait for the patch to be in master before we cut the branch,
> or can the changes be backported afterwards?
I'd like to see the IPv6 support included in 8.2, if possible.
https://sourceware.org/ml/gdb-patches/2018-05/msg00629.html
Eli has made a few comments about the documentation part, and I
addressed everything. I'm still waiting for a code review; I intend to
ping the patch today.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2018-05-31 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 23:09 Joel Brobecker
2018-05-31 9:23 ` Alan Hayward
2018-05-31 18:35 ` Philippe Waroquiers
2018-05-31 18:35 ` Pedro Alves
2018-05-31 21:20 ` Philippe Waroquiers
2018-05-31 19:40 ` Sergio Durigan Junior [this message]
2018-06-01 17:27 ` Joel Brobecker
2018-06-01 21:42 ` Pedro Franco de Carvalho
2018-06-11 22:52 ` 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=87efhrvfkb.fsf@redhat.com \
--to=sergiodj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).