Re: GDB 9.1 Release: Creating the branch on *WED* Dec 11th!

[Eli Zaretskii <eliz@gnu.org>]

> Date: Sat, 14 Dec 2019 00:47:44 +0100
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: tromey@adacore.com, gdb-patches@sourceware.org
> 
> > Does this mean the pretest published yesterday doesn't represent the
> > upcoming release well enough, as these changesets are still part of
> > it?  If so, can we please have a better pretest soon?  I planned on
> > building the pretest on MinGW soon, as I've seen many changes that
> > might "need work" in the MinGW port.
> 
> What we mean is that we we will not be including these patches in
> the GDB 9.1 release.

But they are included in the pretest tarball?

> One thing I'd like to suggest is if you could do a first pre-check
> when I announce that the branch creation is a few days away.
> If you find something sufficiently bad, this would be grounds
> for me to either hold the branch creation, or else hold the
> creation of the pre-release.  I don't who else could help with that,
> because I don't anyone but you building GDB with the configuration
> that you use -- I know we build a MinGW version of GDB on Windows,
> but we use MinGW64 and do not see the issues that you have been
> reporting in the past -- so aside from you, I don't know who else
> can do it.

Thanks, I'm okay with testing the first pretest, and fixing any
problems in the release branch.  I was asking whether the current
pretest is a good approximation for the release, as I don't enjoy
solving problems I don't need to solve, and Gnulib has been
historically an important source of problems for MinGW.

If there are significant changes (not bugfixes) expected before the
release, I'd prefer a pretest after those changes.  I'm not sure I
understand what was the decision regarding the specific issue
mentioned above, if there was a decision.  Am I missing something.