[news.eclipse.technology.kepler] Re: more information

[Nick Chalko <nick@xxxxxxxxxx>]

John Casey wrote:

> Also - and perhaps more foundational - you have to consider the 
> stability needs for a group of interrelated projects. Successive 
> releases will immediately feed in as dependencies of upstream projects, 
> which may in turn feed in further upstream. In order to achieve any sort 
> of reliability in this development model, you have to have solid, 
> automated builds that produce reliable results. Ideally, these builds 
> should be run without intervention, to enable build errors to be 
> reported in a timely way. Kepler is also keenly interested in providing 
> a good way to work with this infrastructure for building software...to 
> make the normal IDE build as similar as possible to the automated build, 
>  to provide notifications to developers inside their IDEs, etc.

The flow and relationship between projects is a very interesting problem 
that has also has a social component.  I did some work on this as part 
of the gump project at apache (http://gump.apache.org).

Gump is a automated build system that builds the latest of EVERYTHING 
against the latest of everything.  Helping to communicate interprocess 
breakages early.  Gump is another tool we should consider as a potential 
integration point.

R,
Nick