Creating the gdb-6.7 branch soon (3 weeks to go?)

Creating the gdb-6.7 branch soon (3 weeks to go?)

[Joel Brobecker]

Hello everyone,

We're getting close to the planned branching date for the next GDB
release. Branching is planned May 27, a first pre-release 2 weeks
after, followed by an official release again 2 weeks after.

I've noticed that development was quite active the past few weeks,
so if the planned dates are interfering with some ongoing work that
you'd like to finish before branching, let us know.

Cheers,
-- 
Joel

Re: Creating the gdb-6.7 branch soon (3 weeks to go?)

[Daniel Jacobowitz]

On Mon, May 07, 2007 at 11:28:44AM -0700, Joel Brobecker wrote:
> Hello everyone,
> 
> We're getting close to the planned branching date for the next GDB
> release. Branching is planned May 27, a first pre-release 2 weeks
> after, followed by an official release again 2 weeks after.
> 
> I've noticed that development was quite active the past few weeks,
> so if the planned dates are interfering with some ongoing work that
> you'd like to finish before branching, let us know.

Doesn't make much difference to me; but if I haven't dealt with the
signed/unsigned char display issue by then, please remind me about it.
Whatever change we decide to make we should do it before 6.7.  I've
been meaning to come back to that.

-- 
Daniel Jacobowitz
CodeSourcery

Re: Creating the gdb-6.7 branch soon (3 weeks to go?)

[Mark Kettenis]

> Date: Mon, 7 May 2007 11:28:44 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> 
> Hello everyone,
> 
> We're getting close to the planned branching date for the next GDB
> release. Branching is planned May 27, a first pre-release 2 weeks
> after, followed by an official release again 2 weeks after.

It doesn't really work for me; I'll be travelling during most of that
period.

Re: Creating the gdb-6.7 branch soon (3 weeks to go?)

[Joel Brobecker]

> > We're getting close to the planned branching date for the next GDB
> > release. Branching is planned May 27, a first pre-release 2 weeks
> > after, followed by an official release again 2 weeks after.
> 
> It doesn't really work for me; I'll be travelling during most of that
> period.

Given the number of platforms that Mark would be able to test, and
given that there is no imperative that we release by a certain date,
I propose we revise the dates to be:

  - Branch date: June 10th
  - Pre-release: June 24th
  - Release    : July 8th (probably 9th, which is a Monday, actually)

That should give Mark enough time to test his configurations before
the pre-release.

Any objection?

-- 
Joel