Re: [Flightgear-devel] development process

2007-07-17 Thread Curtis Olson
On 7/17/07, Tim Moore <[EMAIL PROTECTED]> wrote: I agree with the observations and suggestions that John made. I also agree that the development process isn't really broken, but there is frustration with the slow pace of releases. FlightGear is not a huge project, but it is pretty big and faces

Re: [Flightgear-devel] development process

2007-07-17 Thread Mike Schuh
On Tue, 17 Jul 2007, Tim Moore wrote: >Some projects with which I've been involved use a system of time-boxed >releases. For example, every 2 months a branch is made from the main >source tree and becomes a release, ready or not. Automatic testing helps >with this strategy -- of course it helps in

Re: [Flightgear-devel] development process

2007-07-17 Thread Tim Moore
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Denker wrote: > On 07/16/2007 01:10 PM, Stuart Buchanan made a number of excellent points: > >> A far better approach is to look at how we can make our processes >> more efficient so that the management (of which you are the CEO) can >> make bet

[Flightgear-devel] development process (was: chaos...)

2007-07-16 Thread John Denker
On 07/16/2007 01:10 PM, Stuart Buchanan made a number of excellent points: > A far better approach is to look at how we can make our processes > more efficient so that the management (of which you are the CEO) can > make better use of their time. I think what is required is more > delegation. >