Schedule proposal for the next release(s)

Schedule proposal for the next release(s)

[Joel Brobecker]

Hello,

Now that GDB 6.5 is out, here is what I propose in terms of the next
major release schedule (in all likeliness labled GDB 6.6).

I would like to schedule the next release around begining of Dec 2006.
Working backwards, and substracting a month from it, it would mean that
we need to branch early Nov 2006. Allowing for unexpected problems,
let's give us another 2 weeks, that would mean actual branching date
around Oct 15. So I propose:

        * Branch      : 16-OCT-2006
        * Pre-release : 06-NOV-2006   (3 weeks later)
        * Release     : 20-NOV-2006   (2 weeks after)

I think that should give us enough time to do some testing before
the pre-release and then before the release.

Opinions?

Also, around the same topic, I mentioned to the GDB developers that
the question of making a minor release of the GDB 6.5 branch is still
open. Decision in a couple of month at the latest, depending on what
critical fixes we have.

-- 
Joel

Re: Schedule proposal for the next release(s)

[Nick Roberts]

 > Now that GDB 6.5 is out, here is what I propose in terms of the next
 > major release schedule (in all likeliness labled GDB 6.6).
 > 
 > I would like to schedule the next release around begining of Dec 2006.
 > Working backwards, and substracting a month from it, it would mean that
 > we need to branch early Nov 2006. Allowing for unexpected problems,
 > let's give us another 2 weeks, that would mean actual branching date
 > around Oct 15. So I propose:
 > 
 >         * Branch      : 16-OCT-2006
 >         * Pre-release : 06-NOV-2006   (3 weeks later)
 >         * Release     : 20-NOV-2006   (2 weeks after)

If this is agreed I think it should be added to:

http://sourceware.org/gdb/schedule/

which is already out of date.

On a releated note, I think that http://sourceware.org/gdb/current/ need
not mention dejagnu.

-- 
Nick                                           http://www.inet.net.nz/~nickrob

Re: Schedule proposal for the next release(s)

[Joel Brobecker]

> If this is agreed I think it should be added to:
> 
> http://sourceware.org/gdb/schedule/

Yes, it will be. I thought I would discuss this with the rest of
the community before posting it on the website. Note that our schedule
is only informative and there is no guaranty at all that we'll actually
follow it.

> On a releated note, I think that http://sourceware.org/gdb/current/ need
> not mention dejagnu.

Will take care of that.

-- 
Joel

Re: Schedule proposal for the next release(s)

[Joel Brobecker]

Hello,

> If this is agreed I think it should be added to:
> 
> http://sourceware.org/gdb/schedule/
> 
> which is already out of date.

Page updated.

> On a releated note, I think that http://sourceware.org/gdb/current/ need
> not mention dejagnu.

A patch for this is in the queue.

-- 
Joel

Re: Schedule proposal for the next release(s)

[Nick Roberts]

 > > If this is agreed I think it should be added to:
 > > 
 > > http://sourceware.org/gdb/schedule/
 > > 
 > > which is already out of date.
 > 
 > Page updated.

Thanks.  I think the release schedule is a good idea is it gives developers an
expectation and they can plan accordingly. With Emacs there is no schedule. :-(

On the release history, the only things I find interesting are the number and
the actual release date.  It might also be a good idea to link to the NEWS
file (not to be confused with the current link to News).  Slippage makes me
think of performance reviews where the manager wants to know why the release
was late but does not appreciate the quality of the release.


-- 
Nick                                           http://www.inet.net.nz/~nickrob