dolfin team mailing list archive

[Johan Jansson <jjan@xxxxxxxxxxx>]

On Thu, Oct 26, 2006 at 05:06:21PM +0200, Anders Logg wrote:
> I have just two concerns:
> 
>   1. I would like to see more people helping out with general
>   development and maintenance.

Yes, I think we all do.

>   2. I would like changes to be propagated to the main tree in
>   small pieces (if they are not independent) so I know what is
>   happening and get a chance to influence the development.

Do you mean in the kernel or in all modules/applications as well? I
think it would be counter-productive to demand that application
developers have to submit to a certain check-in schedule (piece by
piece).

Otherwise a simple solution where I think everyone would be happy
would be to have one branch where the kernel is stable which is used
to develop modules/applications (since they won't sabotage eachother),
and one branch where the kernel is unstable, but where very little
application development is done (perhaps only a few simple test
cases). The two branches could then be merged at regular intervals (at
releases for example).

This would give us the collaborative "workshop" which we want in
DOLFIN while at the same time providing stability for application
developers.

> 
>   I don't want to track the development in a separate KTH branch.
> 
> I'll support any development model that does this.

  Johan