Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: heads up: one week to 8.0.1 planned release time
Date: Mon, 28 Aug 2017 13:50:00 -0000	[thread overview]
Message-ID: <20170828135048.56es2tsqsog2vuv2@adacore.com> (raw)

Hello everyone,

The 8.0.1 release is currently planned for next Monday (Sep 4th).
I took a look at the list of PRs still open, and only found one
which wasn't a regressions, so I do not consider it blocking.

I also looked at the list of PRs fixed since 8.0. It must have been
a very good release, since we only fixed 5 PRs since then!

Anything blocking that we need to be aware of?

Assuming nothing comes up, should we go ahead with the 8.0.1 release
next week, or do we want to wait a bit to see if we can find other
issues we might want to fix before 8.0.1 comes out? (personally,
I would go ahead with the 8.0.1, with the option of scheduling
8.0.2 if we end up finding something we really want for the 8.0.x
branch; otherwise, 8.1 will be a mere 3 months later).

Thanks!
-- 
Joel


             reply	other threads:[~2017-08-28 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 13:50 Joel Brobecker [this message]
2017-08-28 21:31 ` Simon Marchi
2017-08-31  7:48   ` Joel Brobecker
2017-09-05 16:13     ` Simon Marchi

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=20170828135048.56es2tsqsog2vuv2@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