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

[Joel Brobecker <brobecker@adacore.com>]

> > > 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?

They are not going to be included at all, neither in the pretest,
nor in the release. Basically, this patch was identified as a candidate
for having it in the 9.1 release. However, upon realizing what the patch
entails, it was deemed to disruptive to be considered for inclusion in
the GDB 9 release cycle.

> 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.

I believe you can do your pretest now. As far as I know, there aren't
any patches known to be pending (we cleared the "want" list prior to
creating the branch).

-- 
Joel