Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: GDB 8.3 release -- time to start the release process
Date: Sat, 15 Dec 2018 12:24:00 -0000	[thread overview]
Message-ID: <20181215122354.GB9867@adacore.com> (raw)

Hello everyone,

It's hard to believe it, but it might be time to start working on
the next major release. For now, I'm labeling that next release
as 8.3, but I have not forgotten the discussion about changing
the versioning.

If we are to target the date that we published, we would want to
create the branch around Jan 15th. So we are about a month away.

As always, I created a wiki page to help track the various activities
around the release process. In particular, it provides links to
bugzilla queries giving us a list of PRs targetting 8.3:

    https://sourceware.org/gdb/wiki/GDB_8.3_Release

Let's start a list of items we'd like to look into before we branch:

  * [JoelB] <NO PR>
    GDB crash or timeout on Windows native

        I do not have much information yet, as I haven't had time
        to investigate. But it looks like we're having timeouts
        or crashes. They seem specific to Windows Server 2016,
        and the problem must have appeared between Nov 19th and
        Nov 26th.

        My plan is to take a look at it during the Xmas break.

Anything else? As far as I can tell, we currently have no PR listed
for 8.3 (https://sourceware.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&list_id=45369&product=gdb&query_format=advanced&target_milestone=8.3)!

Thank you!
-- 
Joel


             reply	other threads:[~2018-12-15 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-15 12:24 Joel Brobecker [this message]
2018-12-15 12:55 ` Eli Zaretskii

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=20181215122354.GB9867@adacore.com \
    --to=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