From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
To: Joel Brobecker <brobecker@adacore.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: GDB 12 preparation and target date?
Date: Fri, 28 Jan 2022 09:40:19 +0000 [thread overview]
Message-ID: <DM6PR11MB3884B7011239E56AB80B0CB0C4229@DM6PR11MB3884.namprd11.prod.outlook.com> (raw)
In-Reply-To: <Ye01Pk+wvX77Hf0V@adacore.com>
On Sunday, January 23, 2022 12:00 PM, Joel Brobecker wrote:
> Hi everyone,
>
> Now that GDB 11.2 (corrective release) is out, we can start discussing
> the next release, which should be GDB 12.
>
> I propose we aim for the following dates:
>
> - GDB 12 branching 2 months from now (~Mar 20-25);
> - GDB 12.1 release 2 weeks later, so early Apr.
>
> In terms of patches, I think it would be useful to start listing
> the fixes and enhancements we'd like to include in GDB 12, and
> keep track of them. If possible, it helps if the patches have
> a corresponding GDB PR with the the target milestone set to 12.1.
Hi,
I propose this bug to be targeted for the 12.1 release, since it seems
like a regression:
https://sourceware.org/bugzilla/show_bug.cgi?id=28833
I couldn't change the target milestone myself.
Thanks
-Baris
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2022-01-28 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 11:00 Joel Brobecker
2022-01-26 15:07 ` Tom Tromey
2022-01-27 3:54 ` Joel Brobecker
2022-01-28 3:03 ` Tiezhu Yang
2022-01-28 9:40 ` Aktemur, Tankut Baris [this message]
2022-02-02 17:00 ` Andrew Burgess
2022-02-02 19:31 ` John Baldwin
2022-02-13 14:33 ` Joel Brobecker
2022-02-14 18:51 ` John Baldwin
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=DM6PR11MB3884B7011239E56AB80B0CB0C4229@DM6PR11MB3884.namprd11.prod.outlook.com \
--to=tankut.baris.aktemur@intel.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).