This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gcc development schedule [Re: sharing libcpp between GDB andGCC]
- From: Andreas Jaeger <aj at suse dot de>
- To: David Edelsohn <dje at watson dot ibm dot com>
- Cc: Richard Henderson <rth at redhat dot com>,Zack Weinberg <zack at codesourcery dot com>, Jim Blandy <jimb at redhat dot com>,gcc at gcc dot gnu dot org, gdb at sources dot redhat dot com
- Date: Wed, 27 Mar 2002 06:32:01 +0100
- Subject: Re: gcc development schedule [Re: sharing libcpp between GDB andGCC]
- References: <200203262236.RAA26398@makai.watson.ibm.com>
David Edelsohn <dje@watson.ibm.com> writes:
>>>>>> Richard Henderson writes:
>
> Richard> I think this is a mistake. It is completely unreasonable to have
> Richard> the entire "major structural changes" time period concurrent with
> Richard> "please work on making a release happen".
>
> Richard> I've been working under the assumption that the current schedule can
> Richard> be changed, so that I can help Diego with the language independent
> Richard> tree-ish IL after the 3.1 release.
>
> I agree. We do not have enough developer bandwidth to work on
> major, new changes concurrently with the release process. Even after GCC
> 3.1.0 is released, we will need to assess how much effort will be required
> for the GCC 3.1.1 bug-fix release the following quarter.
<AOL> I agree, too</AOL>.
Even if development is done on branches, it takes time to bring
changes back into mainline in a clean way: test them properly on
various platforms, split them in small pieces, get them reviewed,...
2 months is not enough for this - and then you should be working on
the same time on getting a good release out. An 8 or 10 month release
cycle seems more approbriate with the GCC man power.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj