From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11173 invoked by alias); 27 Mar 2002 06:54:33 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 11087 invoked from network); 27 Mar 2002 06:54:31 -0000 Received: from unknown (HELO emf.net) (205.149.0.20) by sources.redhat.com with SMTP; 27 Mar 2002 06:54:31 -0000 Received: (from lord@localhost) by emf.net (K/K) id WAA29550; Tue, 26 Mar 2002 22:54:29 -0800 (PST) Date: Tue, 26 Mar 2002 22:54:00 -0000 From: Tom Lord Message-Id: <200203270654.WAA29550@emf.net> To: aj@suse.de CC: neil@daikokuya.demon.co.uk, rth@redhat.com, zack@codesourcery.com, jimb@redhat.com, gcc@gcc.gnu.org, gdb@sources.redhat.com In-reply-to: (message from Andreas Jaeger on Wed, 27 Mar 2002 07:39:49 +0100) Subject: Re: gcc development schedule [Re: sharing libcpp between GDB and GCC] References: <20020325234047.127345EA11@zwingli.cygnus.com> <20020326040735.GM23331@codesourcery.com> <20020326142901.B16366@redhat.com> <20020326231730.GA1283@daikokuya.demon.co.uk> <200203262330.PAA01597@emf.net> X-SW-Source: 2002-03/txt/msg00273.txt.bz2 Further enhancing the testing infrastructure is one objective that I'd like to see and where I've worked on already, Yes. The GCC project has _very_noticably_ improved in many process areas since roughly the time the SC came on-line. I come from a very "software tools" oriented background. I think there's a lot of leverage to be obtained not by waiting for volunteers to contribute things that happen to be useful, but by making an aggressive, worked-out plan and then asking how it can be implemented via funded projects. The SC mission statement contains lofty goals, but it isn't an aggressive, actionable plan for the most part. The list discussions contain many good ideas and initiatives, but overall, that's a scattershot rather than an especially organized approach to the problem. And it's an issue that's both larger than GCC, but to which GCC can make a very useful contribution. Well designed tools for improving the GCC process will work for other projects as well. At the same time, GCC, more than most projects, exemplifies both the strengths and challenges of open source processes -- an emerging software engineering discipline of exponentially increasing commercial and social importance. -t