GDB 8.0 release update (2017-05-19)

GDB 8.0 release update (2017-05-19)

[Joel Brobecker]

Hello,

It's been a couple of weeks since we announced the first 8.0 pre-release.
Thanks to everyone who reported (and fixed!) the issues they found so far.

If I kept track of everything properly, I think we fixed all
the known blocking issues. The area where I might be wrong about
that are the libiberty patches for MinGW. Eli?

Any other issues I missed?

If not, I propose a release on Wed, May 24th (May twenty fourth be with
you? -- sorry)

Thanks!
-- 
Joel

Re: GDB 8.0 release update (2017-05-19)

[Eli Zaretskii]

> Date: Fri, 19 May 2017 11:30:06 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> 
> If I kept track of everything properly, I think we fixed all
> the known blocking issues. The area where I might be wrong about
> that are the libiberty patches for MinGW. Eli?

They are in the works, but not there yet.  I hope they will be ready
by the date you want to make the release, but I cannot be sure.

Re: GDB 8.0 release update (2017-05-19)

[Joel Brobecker]

Hi Eli,

> > If I kept track of everything properly, I think we fixed all
> > the known blocking issues. The area where I might be wrong about
> > that are the libiberty patches for MinGW. Eli?
> 
> They are in the works, but not there yet.  I hope they will be ready
> by the date you want to make the release, but I cannot be sure.

As far as I can tell, at least 1 patch is still being discussed,
and the others should be in; is that correct? Would you mind dropping
me a note when we're good to go for the release?

-- 
Joel

Re: GDB 8.0 release update (2017-05-19)

[Eli Zaretskii]

> Date: Wed, 24 May 2017 08:49:39 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> > They are in the works, but not there yet.  I hope they will be ready
> > by the date you want to make the release, but I cannot be sure.
> 
> As far as I can tell, at least 1 patch is still being discussed,
> and the others should be in; is that correct?

I think there are two not yet committed into libiberty.  There's also
one for GDB.

> Would you mind dropping me a note when we're good to go for the
> release?

Will do.

Re: GDB 8.0 release update (2017-05-19)

[Eli Zaretskii]

> Date: Wed, 24 May 2017 21:06:18 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> CC: gdb-patches@sourceware.org
> 
> > Date: Wed, 24 May 2017 08:49:39 -0700
> > From: Joel Brobecker <brobecker@adacore.com>
> > Cc: gdb-patches@sourceware.org
> > 
> > > They are in the works, but not there yet.  I hope they will be ready
> > > by the date you want to make the release, but I cannot be sure.
> > 
> > As far as I can tell, at least 1 patch is still being discussed,
> > and the others should be in; is that correct?
> 
> I think there are two not yet committed into libiberty.  There's also
> one for GDB.
> 
> > Would you mind dropping me a note when we're good to go for the
> > release?
> 
> Will do.

We are not yet there, but here's an update: 2 out of 3 libiberty
changes are committed to the GCC tree, the 3rd should be there soon, I
hope.

Once that happens, I guess I should push them all to the GDB master,
and then cherry-pick to the 8.0 branch, is that right?

Re: GDB 8.0 release update (2017-05-19)

[Joel Brobecker]

> We are not yet there, but here's an update: 2 out of 3 libiberty
> changes are committed to the GCC tree, the 3rd should be there soon, I
> hope.

Thanks for the update, Eli.

> Once that happens, I guess I should push them all to the GDB master,
> and then cherry-pick to the 8.0 branch, is that right?

That's correct :).

-- 
Joel

Re: GDB 8.0 release update (2017-05-19)

[Eli Zaretskii]

> Date: Tue, 30 May 2017 05:44:57 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org, DJ Delorie <dj@redhat.com>
> 
> > We are not yet there, but here's an update: 2 out of 3 libiberty
> > changes are committed to the GCC tree, the 3rd should be there soon, I
> > hope.
> 
> Thanks for the update, Eli.
> 
> > Once that happens, I guess I should push them all to the GDB master,
> > and then cherry-pick to the 8.0 branch, is that right?
> 
> That's correct :).

Now done.  GDB 8.0 is good to go, as far as MinGW build is concerned.
Sorry for the delay.

Re: GDB 8.0 release update (2017-05-19)

[Joel Brobecker]

> Now done.  GDB 8.0 is good to go, as far as MinGW build is concerned.

Thanks, Eli. I've just finished making the release now :)

> Sorry for the delay.

No worries. Thanks for catching all the issues and helping get them
fixed. Let's also not forget those who jumped in, and helped as well!

-- 
Joel